Methods and systems for providing access to a computing environment

ABSTRACT

A method for providing access to a computing environment includes the step of receiving, by a broker machine, a request from a client machine for access to a computing environment, the request including an identification of a user of the client machine. One of a plurality of virtual machines is identified, the identified virtual machine providing the requested computing environment. One of a plurality of execution machines is identified, the identified execution machine executing a hypervisor providing access to hardware resources required by the identified virtual machine. A connection is established between the client machine and the identified virtual machine.

RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication Ser. No. 60/761,674, entitled “Methods and Systems forProviding Access to a Computing Environment,” filed Jan. 24, 2006, whichis incorporated herein by reference.

FIELD OF THE INVENTION

The invention generally relates to providing access to computingenvironments. More particularly, the invention relates to methods andsystems for establishing a connection between a client system and avirtual machine.

BACKGROUND INFORMATION

Desktop deployment strategies, such as personal desktop deployment orserver-based computing deployment strategies, suffer from drawbacks.Conventional desktop PC deployment strategies create significantproblems with management, upgrade cycles and support requirements thatdirectly translate into a high total cost of ownership. Each desktop PCis installed on the user's desktop, and any hardware maintenancetypically requires IT personnel to come to the user's desk.Additionally, PCs age rapidly and are usually replaced on a recurringbasis as the hardware becomes dated and/or obsolete. Remote access anddistributed, multi-office deployments may amplify these problems.

A server-based computing model solves many of the desktop PC deploymentmodel problems, but at the expense of a less flexible environment. Intypical server-based computing architectures, each server hosts a numberof users and applications, meaning that one user or application mayaffect the performance perceived by other users served by the sameserver. The performance issue associated with thin clients may result inenterprises using server-based computing only for specific nicheapplications, such as remote access applications. The deploymentstrategy of combining the desktop PC and the thin client/server-basedcomputing model is subject to these same limitations as each PC stillneeds to be managed, and the operating system and software may stillneed to be patched and updated. It would be desirable to provide asystem having a lower total cost of ownership of traditionalserver-based computing systems while avoiding the performancedegradation those systems can suffer.

SUMMARY OF THE INVENTION

In one aspect, problems of current desktop deployment strategies areaddressed. An array of inexpensive physical machines may be partitionedinto multiple virtual machines, creating a virtual PC for each user. Thephysical machines may be servers such as rack-mount servers, bladeservers, or stand-alone servers. The physical machines may also beworkstations or workstation blades or personal computers. A policy-baseddynamic deployment system provisions the virtual machines and associatesthe virtual machine with an execution machine (i.e., a physical machine)and a user. Centralized hosting provides the manageability ofserver-based computing while the dedicated environment provides theflexibility and compatibility with applications that a desktop PCenables. However, the system has a much lower total cost ofownership—because the system is implemented in software, rather thanbeing dependent on hardware, the system has a much lower total cost ofownership.

In another aspect, the hardware lifecycle may be extended by increasingthe amount of hardware resources assigned to virtual machines ascomputational demands increase over time. Additionally, the use ofvirtualization eases the difficulty in dealing with multiple OS images.

In one embodiment, machines are configured to run multiple copies of oneor more operating systems (e.g. different versions/releases of WINDOWSfrom Microsoft Corporation). Users transmit requests for access tocomputing resources to the deployment system, which may use aconfiguration policy to decide how (with what physical and/or virtualresources) and where (on which physical machine in the machine farm andon which virtual machine) to provide access to the requested computingresource. The virtual machine can be created on demand, and therequested software resource may be downloaded and installed in thevirtual machine as required. Alternatively, the virtual machine may bepre-configured with a plurality of software and/or virtual hardwareresources to provide a particular computing environment to the user. Theuser request is directed to the selected, configured virtual machine anda remote display connection is established between the virtual machineand a remote display client on the user's access device, which will bereferred to generally as a “client machine.” Devices such as CD-ROMdrives, floppy drives, USB drives and other similar devices that areconnected to the client machine are connected and remotely accessible tothe virtual machine, thereby allowing the use of these devices in amanner similar to a standard desktop computer.

A deployment system may manage a pool of virtual machines (a machinefarm) to which new virtual machines can be added on demand.Alternatively, a plurality of software modules, including a sessionmanagement component and a virtual machine management component mayprovide management functionality. Executing virtual machines may bemigrated from one physical machine to another, under control of thedeployment system, to provide load balancing or to facilitate hardwaremaintenance. Inactive virtual machines may be suspended to free physicalcomputing resources. Active virtual machines may be migrated from onephysical machine to another to consolidate them onto a smaller number ofphysical machines to allow the unused physical machines to be shutdownto save power during off-peak periods or to free the physical resourceto be re-assigned for a different purpose e.g. process web requests.Suspended virtual machines may be resumed prior to users requiringaccess. This can be done manually or automatically via policies orpreferences or through a learning process by monitoring a user'sbehavior over time.

Performance requirements of the requested resource may be consideredwhen allocating computing resources to virtual machines. For example, afinancial analysis package may require twice as many CPU resources as ageneric productivity application, such as those included in MICROSOFTOFFICE, manufactured by Microsoft Corporation of Redmond, Wash. Avirtual machine providing the financial analysis package may execute ona physical machine determined to have sufficient spare computationalcapacity, or existing virtual machines may be relocated to otheravailable physical machines to ensure sufficient available capacity on aparticular physical machine.

Each user is provided a separate virtual machine environment, whichprovides increased flexibility in that each user may run any version orconfiguration of an operating system independently of other users andalso allows users to run potentially dangerous or destabilizingapplications with little risk of affecting other users. This isparticularly useful for developers/testers/information technologypersonnel who frequently need to re-install and modify the operatingsystem and run potentially destabilizing applications.

Since sharing computing resources and CPU scheduling occurs outside ofthe virtual machine environment, users can run computing-resourceintensive resources with no risk of affecting other users. Virtualmachines also provide increased security isolation between users.Because each user is running a separate copy of the OS, there is muchless chance of security breaches and virus infections over thebetween-users boundaries than in the shared OS case.

A solution is also provided for problems that arise from a situationwhere, in a hardware-based system of machines, the hardware is mixed,whether due to an initial purchasing decision or due to the acquisitionof different types of physical machines over time. Even if initially allof the hardware was uniform, purchasing additional hardware to replacefailing modules and increasing the capacity typically leads tonon-uniform hardware throughout a machine farm. Even if all hardware ispurchased from the same vendor, it is likely that the hardware purchasedlater will use different chipsets and components, and will requiredifferent drivers. Non-uniform hardware has traditionally translatedinto the need to maintain multiple versions of the operating systemimages (which means higher costs) and limits flexibility of moving usersbetween machines—because the operating system image may beincompatible—which also translates into higher cost. Virtual machinesallow efficient use of the same operating system image even in ahardware farm that includes heterogeneous machines. The use of the sameoperating system image helps to significantly reduce the managementcost.

Adding remote display capability (e.g. presentation layer protocols,such as ICA, RDP, or X11) to virtualization techniques allowsvirtualization to be used for interactive computing. Hosting multiplevirtual machines on an execution machine allows better utilization ofthe available physical computing resources (e.g.: space, power,processing power, processing capacity, RAM, bandwidth, etc.) therebylowering costs. The use of virtualization also allows hardware to beupdated and maintained independently of OS version and specific devicedrivers hosted in the operating systems or virtual machines.Additionally, virtual machines enhance system security by isolatingcomputing environments from each other.

In still another aspect, a method for providing access to a computingenvironment includes the step of receiving, by a broker machine, arequest from a client machine for access to a computing environment, therequest including an identification of a user of the client machine. Oneof a plurality of virtual machines is identified, the identified virtualmachine providing the requested computing environment. One of aplurality of execution machines is identified, the identified executionmachine executing a hypervisor providing access to hardware resourcesrequired by the identified virtual machine. A connection is establishedbetween the client machine and the identified virtual machine.

In one embodiment, one of the plurality of virtual machines isidentified responsive to the received identification of the user of theclient machine. In another embodiment, the one of the plurality ofexecution machines is identified responsive to an identification ofhardware resources required by the identified virtual machine. In stillanother embodiment, the identified virtual machine is launched in thehypervisor. In yet another embodiment, a connection is establishedbetween the client machine and the identified virtual machine using apresentation layer protocol.

In yet another aspect, in a system providing access to a computingenvironment by a broker machine to a client machine, an executionmachine executing a hypervisor providing access to hardware resourcesrequired by the computing environment, an apparatus comprises anidentification component, an execution component, and a managementcomponent. The identification component is in communication with avirtual machine management component and receives an identification ofone of a plurality of virtual machines, the identified virtual machineproviding a requested computing environment. The execution componentprovisions the identified virtual machine. The management componentestablishes a connection between the client machine and the identifiedvirtual machine.

In one embodiment, a virtual machine service component executing in thehypervisor is in communication with the session management component andreceives configuration information associated with the client machine.In another embodiment, the virtual machine service component executes inthe identified virtual machine. In still another embodiment, theidentification component receives from the broker machine anidentification of one of a plurality of execution machines. In yetanother embodiment, comprises a transceiver receiving an identificationby a user of the client machine of a type of computing environmentrequested and transmitting the identification of the type of computingenvironment requested to the virtual machine management component.

In one embodiment, the virtual machine management component allocatesthe identified virtual machine to a user. In another embodiment, themanagement component further comprises providing an internet protocoladdress associated with the identified virtual machine to the clientmachine. In still another embodiment, the management component furthercomprises providing an internet protocol address associated with theexecution machine to the client machine. In yet another embodiment, themanagement component establishes a connection between the client machineand the virtual machine using a presentation layer protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects of this invention will be readily apparent fromthe detailed description below and the appended drawings, which aremeant to illustrate and not to limit the invention, and in which:

FIG. 1 is a block diagram of one embodiment of an environment in which aclient machine accesses a computing resource provided by a remotemachine;

FIGS. 1A and 1B are block diagrams depicting embodiments of typicalcomputers useful in embodiments with remote machines or client machines;

FIG. 2A is a block diagram of a system for providing access to aresource;

FIG. 2B is a block diagram of one embodiment of a system in which aclient machine can initiate execution of an application program fordetermining the resource neighborhood of that client machine;

FIG. 2C is a block diagram of an embodiment in which a client machineuses a web browser application to determine its resource neighborhood;

FIGS. 3A, 3B, and 3C are block diagrams of embodiments of systems ofcommunication among a client machine and multiple remote machines;

FIG. 3D is a block diagram of one embodiment of a system in which aclient machine can access a resource from a resource neighborhood webpage displayed at that client machine;

FIG. 3E is a block diagram of one embodiment of a system in which aremote machine acts as an intermediary for a machine farm;

FIG. 4 is a block diagram of one embodiment of a resource neighborhoodapplication in which a client machine is in communication with one ofthe remote machines;

FIG. 5 is a block diagram of a computing embodiment in which a clientmachine is in communication with a remote machine having an installedresource neighborhood application program of the invention;

FIG. 6A is a screen shot of an embodiment of a display of a clientmachine after a resource neighborhood application program is executed;

FIG. 6B is a screen shot of another embodiment of a display screen of aclient machine after the resource neighborhood application program isexecuted;

FIG. 7A is a block diagram of an embodiment of a network providingpolicy-based access to application programs for a machine;

FIG. 7B is a block diagram depicting a more detailed embodiment of apolicy engine;

FIG. 8 is a flowchart depicting one embodiment of a process forproviding access to a resource;

FIG. 9 is a flow diagram depicting one embodiment of a process forelecting a management node;

FIG. 10 is a flow diagram depicting one embodiment of a process toupdate information collected by the management node;

FIG. 11 is a block diagram depicting an embodiment of a machine farmincluding first and second network management processes;

FIG. 12 is a block diagram depicting one embodiment of a virtual machinemanagement component;

FIG. 13 is a block diagram depicting one embodiment of a sessionmanagement component;

FIG. 14 is a block diagram depicting one embodiment of a system in whicha drive associated with the client machine 10 is made available to acomputing environment;

FIG. 15A is a block diagram depicting one embodiment of a client machinesupporting multiple client machine display devices;

FIG. 15B is a block diagram depicting one embodiment of a system forsupporting multiple client machine display devices

FIG. 15C is a block diagram depicting one embodiment of a session loginmechanism providing support for multiple client machine display devices;

FIG. 16A is a flow diagram depicting one embodiment of the steps to betaken to provide a desired display layout to a client machine havingmultiple display devices;

FIG. 16B is a flow diagram depicting one embodiment of a process tomodify a window message;

FIG. 16C is a flow diagram depicting one embodiment of the steps takento associate a display layout with a client machine;

FIG. 16D is a flow diagram depicting one embodiment of the steps takento change a desired display layout for a client machine;

FIG. 17 is a block diagram depicting one embodiment of a system in whicha remote machine authenticates the user of a client machine;

FIG. 18 is a flow diagram depicting one embodiment of the steps taken toaccess a plurality of files comprising an application program;

FIG. 19 is a block diagram depicting one embodiment of a client machine10 including an application streaming client, a streaming service and anisolation environment;

FIG. 20 is a flow diagram depicting one embodiment of steps taken by aclient machine to execute an application;

FIG. 21 is a block diagram depicts one embodiment of a plurality ofapplication files;

FIG. 22A is a flow diagram depicting one embodiment of the steps takento enable transparent distributed program execution on a remote machinethrough the selection of graphical indicia representative of a data filelocated on the client machine;

FIG. 22B is a flow diagram depicting one embodiment of the steps takenby a remote machine to enable transparent distributed program executionon a remote machine through the selection of graphical indiciarepresentative of a data file located on the client machine;

FIG. 23 is a flow diagram depicting another embodiment of the stepstaken to enable transparent distributed program execution on a clientmachine through the selection of graphical indicia representative of adata file located on a remote machine;

FIG. 24 is a flow diagram depicting one embodiment of the steps taken tonegotiate the protocol for a connection between a client machine and aremote machine;

FIG. 25 is a block diagram depicting an embodiment of a remote machineand a client machine establishing a protocol stack for communication;

FIG. 26 is a block diagram depicting one embodiment of a client machinearchitecture;

FIG. 27 is a block diagram depicting one embodiment of communicationbetween a client machine and a machine farm;

FIG. 28 is a block diagram depicting one embodiment of a client machinearchitecture;

FIG. 29 is a flow diagram depicting one embodiment of the steps taken todisplay application output in a web page;

FIG. 30 is a flow diagram depicting one embodiment of the steps takenlink to a virtual machine identified by a hyperlink configuration file;

FIG. 31 is a block diagram depicting an embodiment of a systemarchitecture in which a multiplexer is used to transmit data to morethan one client machine;

FIG. 32 is a block diagram depicting another embodiment of a systemarchitecture in which a multiplexer is used to transmit data to morethan one client machine;

FIG. 33 is a block diagram depicting one embodiment of an architecturefor displaying application output in a web page;

FIG. 34 is a block diagram depicting another embodiment of anarchitecture for displaying application output in a web page;

FIG. 35 is a block diagram depicting another embodiment of anarchitecture for displaying application output in a web page;

FIG. 36 is a block diagram depicting another embodiment of anarchitecture for displaying application output in a web page;

FIG. 37 is a block diagram depicting one embodiment of a client machinereceiving window attribute data via a virtual channel;

FIG. 38 is a block diagram depicting a client machine connected to morethan one remote machine;

FIG. 39 is a flow diagram depicting one embodiment of the steps taken todetect and transmit server-initiated display changes;

FIG. 40 is a flow diagram depicting one embodiment of the steps taken todetect and transmit client-initiated display changes;

FIG. 41 is a flow diagram depicting one embodiment for enablingtransmission of seamless windows between a client machine and a remotemachine;

FIG. 42 is a block diagram depicting one embodiment of an agent;

FIG. 43 is a block diagram depicting one embodiment of a system forenabling seamless windowing mode between a client machine and remotecomputing environments;

FIG. 44 is a flow diagram depicting one embodiment of the steps taken ina method of receiving window attribute data and graphical dataassociated with remote windows from virtualized operating systems andfrom native operating systems;

FIG. 45 is a block diagram of a system for providing a client with areliable connection to a host service according to an embodiment of theinvention;

FIG. 46 is a block diagram of a system for providing a client with areliable connection to a host service according to another embodiment ofthe invention;

FIG. 47 depicts communications occurring over a network according to anembodiment of the invention;

FIG. 48 depicts communications occurring over a network according toanother embodiment of the invention;

FIG. 49 depicts a process for encapsulating a plurality of secondaryprotocols within a first protocol for communication over a networkaccording to an embodiment of the invention;

FIG. 50 is a block diagram of an embodiment of a computer system tomaintain authentication credentials in accordance with the invention;

FIG. 51 is a flow diagram of the steps followed in an embodiment of thecomputer system of FIG. 5 to maintain authentication credentials duringa first communication session in accordance with the invention;

FIG. 52 is a flow diagram of the steps followed in an embodiment of thecomputer system of FIG. 50 to maintain authentication credentials duringa second communication session following the termination of the firstcommunication session of FIG. 53A in accordance with the invention;

FIG. 53 is a block diagram of an embodiment of a computer system tomaintain authentication credentials in accordance with anotherembodiment of the invention;

FIG. 54 is a flow diagram of the steps followed in an embodiment of thecomputer system of FIG. 53 to maintain authentication credentials duringa first communication session in accordance with the invention;

FIG. 55 is a flow diagram of the steps followed in an embodiment of thecomputer system of FIG. 53 to maintain authentication credentials duringa second communication session following the termination of the firstcommunication session of FIG. 53 in accordance with the invention;

FIG. 56 is a flow diagram of the steps followed in an embodiment of thecomputer system of FIG. 53 to maintain authentication credentials duringa second communication session following the termination of a secondcommunication channel of the first communication session of FIG. 53 inaccordance with the invention;

FIG. 57 is a block diagram of a system to maintain authenticationcredentials and provide a client with a reliable connection to a hostservice according to an embodiment of the invention;

FIG. 58 is a block diagram of a system to maintain authenticationcredentials and provide a client with a reliable connection to a hostservice according to another embodiment of the invention;

FIG. 59 is a block diagram of a system to maintain authenticationcredentials and provide a client with a reliable connection to a hostservice according to another embodiment of the invention;

FIG. 60 is a block diagram of a system to maintain authenticationcredentials and provide a client with a reliable connection to a hostservice according to another embodiment of the invention;

FIG. 61 is a block diagram of a system for providing a client with areliable connection to a host service and further including componentsfor reconnecting the client to a host service according to an embodimentof the invention;

FIG. 62 is a block diagram of an embodiment of a system for providing aclient with a reliable connection to a host service and furtherincluding components for reconnecting the client to a host service;

FIG. 63 is a block diagram of an embodiment of FIG. 61 further includingcomponents for initially connecting the client to a host service;

FIG. 64 is a block diagram of the system of FIG. 62 further includingcomponents for initially connecting the client to a host service and tomaintain authentication credential according to an embodiment of theinvention;

FIG. 65 is a flow diagram of a method for network communicationsaccording to an embodiment of the invention;

FIG. 66 is a flow diagram of a method for reconnecting the client to thehost services;

FIGS. 67-69 are flow diagrams of a method for connecting a client to aplurality of host services according to an embodiment of the invention;

FIG. 70 is a flow diagram of a method for providing a client with areliable connection to host services and for reconnecting the client tothe host services according to an embodiment of the invention;

FIGS. 71-72 are flow diagrams of a method for reconnecting a client tohost services according to an embodiment of the invention;

FIG. 73 is a conceptual block diagram of an embodiment of clientsoftware and server software;

FIG. 74 is a flow chart of an embodiment of a method for monitoringnetwork performance;

FIG. 75 is a flow chart of an embodiment of a method of operation of theserver software;

FIG. 76 is a flow chart of an embodiment of a method of generatingsub-metrics by the client;

FIG. 77 is a flow chart of an embodiment of a method of generatingsub-metrics by the client;

FIG. 78 is a flow chart of an embodiment of a method of generatingsub-metrics by the server;

FIG. 79 is a schematic diagram depicting a networked client-servercomputing system;

FIG. 80 is a flow chart depicting a method for connecting a clientmachine to disconnected application sessions;

FIG. 81 is a flow chart depicting on embodiment a method for connectingthe client machine to active application sessions;

FIG. 82 is a schematic diagram depicting one embodiment of a clientmachine in communication with several remote machines;

FIG. 83 is a flow diagram depicting one embodiment of steps taken in amethod to connect a user of a client machine to a computing environment;

FIG. 84 is a flow diagram depicting an embodiment of steps taken in amethod to connect a user of a client machine to a computing environmentin response to selection of a graphical user interface element;

FIG. 85 is a block diagram depicting one embodiment of a remote machineable to connect the client machine to an application session;

FIG. 86 is a block diagram of an embodiment of a system for connecting aclient machine to an application session responsive to application of apolicy;

FIG. 87 is a flow diagram depicting the steps taken in one method toconnect a client machine to an application session responsive toapplication of a policy;

FIG. 88 is a block diagram depicting one embodiment of a system forproviding, by a virtual machine, access to a computing environment;

FIG. 89A is a block diagram depicting one embodiment of a storage deviceand a computing device;

FIG. 89B is a flow diagram depicting one embodiment of the steps takenin a method for providing access to a computing environment on acomputing device via a storage device;

FIG. 90A is a block diagram depicting one embodiment of a mobilecomputing device;

FIG. 90B is a flow diagram depicting one embodiment of the steps takenin a method for providing a portable computing environment by a mobilecomputing device;

FIG. 91A is a block diagram of one embodiment of a mobile computingdevice and a computing device;

FIG. 91B is a flow diagram depicting depicts one embodiment of the stepstaken in a method for providing access to a computing environment on acomputing device via a mobile computing device;

FIG. 92A is a block diagram depicting one embodiment of a mobilecomputing device and a computing device comprising a computingenvironment selector;

FIG. 92B is a flow diagram depicting an embodiment of the steps taken ina method for establishing a computing environment on a computing devicevia a mobile computing device;

FIG. 93A is a block diagram depicting one embodiment of a mobilecomputing device connecting to a docking station;

FIG. 93B is a block diagram depicting one embodiment of a dockingstation connecting a mobile computing device and a computing device;

FIG. 93C is a block diagram depicting one embodiment of a mobilecomputing device and computing device having a docking mechanism;

FIG. 93D is a flow diagram depicting one embodiment of the steps takenin a method of providing to a mobile computing device one or morehardware resources;

FIG. 94A is a block diagram depicting one embodiment of a mobilecomputing device having a plurality of processors;

FIG. 94B is a flow diagram depicting one embodiment of the steps takenin a method for switching, by a mobile computing device, between use ofmultiple processors;

FIG. 95 is a block diagram depicting one embodiment of a system forproviding to a first client agent, via a second client agent on a firstremote machine, output data generated by a resource executing in avirtual machine provided by a second remote machine;

FIG. 96 is a block diagram depicting an embodiment of a system forproviding to a first client agent, via a second client agent on a firstremote machine, output data generated by a resource executing in avirtual machine provided by a second remote machine; and

FIG. 97 is a block diagram depicting one embodiment of a system foridentifying, by a coordinator machine, a worker machine providing, via avirtual machine, access to a computing environment.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, a block diagram of one embodiment of anenvironment in which a client machine 10, 10′ accesses a computingresource provided by a remote machine, 30, 30′, 30″, 30′″ is shown.

A remote machine 30 such as remote machine 30, 30′, 30″, or 30′″(hereafter referred to generally as remote machine 30) acceptsconnections from a user of a client machine 10. Although only two clientmachines 10 and only four remote machines 30 are depicted in theembodiment shown in FIG. 1, it should be understood that the system mayprovide multiple ones of any or each of those components. For example,in one embodiment, the system may include multiple, logically-groupedremote machines 30, one or more of which is available to provide aclient machine 10, 10′ access to computing resources. In theseembodiments, the logical group of remote machines may be referred to asa “server farm” or “machine farm,” indicated in FIG. 1A as machine farm38. In some of these embodiments, the remote machines 30 may begeographically dispersed. Thus, the group of remote machines 30logically grouped as a machine farm 38 may be interconnected using awide-area network (WAN) connection, metropolitan-area network (MAN)connection, a local area network (LAN) a storage-area network (SAN), ora public network such as the Internet. For example, a machine farm 38may include remote machines 30 physically located in geographicallydiverse locations around the world, including different continents,regions of a continent, countries, regions of a country, states, regionsof a state, cities, regions of a city, campuses, regions of a campus, orrooms. Data transmission speeds between remote machines 30 in themachine farm 38 can be increased if the remote machines 30 are connectedusing a local-area network (LAN) connection or some form of directconnection. A machine farm 38 may be administered as a single entity.

A centralized service may provide management for machine farm 38. Insome embodiments, one or more remote machines 30 elect a particularremote machine 30 to provide management functionality for the farm. Theelected remote machine 30 may be referred to as a management server,management node, or management process. The management node 30 maygather and store information about a plurality of remote machines 30,respond to requests for access to resources hosted by remote machines30, and enable the establishment of connections between client machines10 and remote machines 30. In other embodiments, an administratordesignates one or more remote machines 30 to provide managementfunctionality for machine farm 38.

Alternatively, management of the machine farm 38 may be de-centralized.In some embodiments, one or more remote machines 30 comprise components,subsystems and modules to support one or more management services forthe machine farm 38. In one of these embodiments, one or more remotemachines 30 provide functionality for management of dynamic data,including techniques for handling failover, data replication, andincreasing the robustness of the machine farm 38. In another of theseembodiments, one or more remote machines 30 include communicationscapabilities to enable the one or more remote machines 30 to interactwith one another to share responsibility for management tasks. Eachremote machine 30 may communicate with a persistent store and, in someembodiments, with a dynamic store.

Persistent store may be physically implemented on a disk, disk farm, aredundant array of independent disks (RAID), writeable compact disc, orany other device that allows data to be read and written and thatmaintains written data if power is removed from the storage device. Asingle physical device may provide storage for a plurality of persistentstores, i.e., a single physical device may be used to provide thepersistent store for more than one machine farm 38. The persistent storemaintains static data associated with each remote machine 30 in machinefarm 38 and global data used by all remote machines 30 within themachine farm 38. In one embodiment, the persistent store may maintainthe server data in a Lightweight Directory Access Protocol (LDAP) datamodel. In other embodiments, the persistent store stores server data inan ODBC-compliant database. For the purposes of this description, theterm “static data” refers to data that do not change frequently, i.e.,data that change only on an hourly, daily, or weekly basis, or data thatnever change.

The data stored by the persistent store may be replicated forreliability purposes physically or logically. For example, physicalredundancy may be provided using a set of redundant, mirrored disks,each providing a copy of the data. In other embodiments, the databaseitself may be replicated using standard database techniques to providemultiple copies of the database. In further embodiments, both physicaland logical replication may be used concurrently.

As described above, the remote machines 30 store “static” data, i.e.,data that persist across client sessions, in the persistent store.Writing to the persistent store can take relatively long periods oftime. To minimize accesses to the persistent store, the remote machines30 may develop a logical, common database (i.e., the dynamic store) thatis accessible by all of the remote machines 30 in the machine farm 38for accessing and storing some types of data. The dynamic store may bephysically implemented in the local memory of a single or multipleremote machines 30 in the machine farm 38. The local memory can berandom access memory, disk, disk farm, a redundant array of independentdisks (RAID), or any other memory device that allows data to be read andwritten.

In general, data stored in the dynamic store are data that are typicallyqueried or changed frequently during runtime. Examples of such data(hereafter referred to as runtime data) are the current workload levelfor each of the remote machines 30 in the machine farm 38, the status ofthe remote machines 30 in the machine farm 38, client session data, thenumber of virtual machines supported by a remote machine 30, theidentity of the operating systems supported by a remote machine 30, andlicensing information.

In one embodiment, the dynamic store comprises one or more tables, eachof which stores records of attribute-value pairs. Any number of tablesmay exist, but each table stores records of only one type. Tables are,in some embodiments identified by name. Thus, in this embodiment, tworemote machines 30 that use the same name to open a table refer to thesame logical table.

The dynamic store (i.e., the collection of all record tables) can beembodied in various ways. In one embodiment, the dynamic store iscentralized; that is, all runtime data are stored in the memory of oneremote machine 30 in the machine farm 38. That server operates in amanner similar to the management node described above, that is, allother remote machines 30 in the machine farm 38 communicate with theserver acting as the centralized data store when seeking access to thatruntime data. In another embodiment, each remote machine 30 in themachine farm 38 keeps a full copy of the dynamic store. Here, eachremote machine 30 communicates with every other remote machine 30 tokeep its copy of the dynamic store up to date.

In another embodiment, each remote machine 30 maintains its own runtimedata and communicates with every other remote machine 30 when seeking toobtain runtime data from them. Thus, for example, a remote machine 30attempting to find an application program requested by the clientmachine 10 may communicate directly with every other remote machine 30in the machine farm 38 to find one or more servers hosting the requestedapplication.

For machine farms 38 having a large number of remote machines 30, thenetwork traffic produced by these embodiments can become heavy. Oneembodiment alleviates heavy network traffic by designating a subset ofthe remote machines 30 in a machine farm 38, typically two or more, as“collector points.” Generally, a collector point is a server thatcollects run-time data. Each collector point stores runtime datacollected from certain other remote machines 30 in the machine farm 38.Each remote machine 30 in the machine farm 38 is capable of operatingas, and consequently is capable of being designated as, a collectorpoint. In one embodiment, each collector point stores a copy of theentire dynamic store. In another embodiment, each collector point storesa portion of the dynamic store, i.e., it maintains runtime data of aparticular data type. The type of data stored by a remote machine 30 maybe predetermined according to one or more criteria. For example, remotemachines 30 may store different types of data based on their boot order.Alternatively, the type of data stored by a remote machine 30 may beconfigured by an administrator using administration tool 140. In theseembodiments, the dynamic store is distributed among two or more remotemachines 30 in the machine farm 38.

Remote machines 30 not designated as collector points know the remotemachines 30 in a machine farm 38 that are designated as collectorpoints. A remote machine 30 not designated as a collector pointcommunicates with a particular collector point when delivering andrequesting runtime data. Consequently, collector points lighten networktraffic because each remote machine 30 in the machine farm 38communicates with a single collector point remote machine 30, ratherthan with every other remote machine 30, when seeking to access theruntime data.

The machine farm 38 can be heterogeneous, that is, one or more of theremote machines 30 can operate according to one type of operating systemplatform (e.g., WINDOWS NT, manufactured by Microsoft Corp. of Redmond,Wash.), while one or more of the other remote machines 30 can operateaccording to another type of operating system platform (e.g., Unix orLinux). Additionally, a heterogeneous machine farm 38 may include one ormore remote machines 30 operating according to a type of operatingsystem, while one or more other remote machines 30 execute one or moretypes of hypervisors rather than operating systems. In theseembodiments, hypervisors may be used to emulate virtual hardware,partition physical hardware, virtualize physical hardware, and executevirtual machines that provide access to computing environments.Hypervisors may include those manufactured by VMWare, Inc., of PaloAlto, Calif.; the Xen hypervisor, an open source product whosedevelopment is overseen by XenSource, Inc., of Palo Alto; theVirtualServer or virtual PC hypervisors provided by Microsoft or others.

In some embodiments, a hypervisor executes on a machine executing anoperating system. In one of these embodiments, a machine executing anoperating system and a hypervisor may be said to have a host operatingsystem (the operating system executing on the machine), and a guestoperating system (an operating system executing within a computingresource partition provided by the hypervisor). In other embodiments, ahypervisor interacts directly with hardware on a machine, instead ofexecuting on a host operating system. In one of these embodiments, thehypervisor may be said to be executing on “bare metal,” referring to thehardware comprising the machine.

Remote machines 30 may be servers, file servers, application servers,appliances, network appliances, gateways, application gateways, gatewayservers, virtualization servers, deployment servers, or firewalls. Theremote machine 30 may be an SSL VPN server. The remote machine 30 may bean application acceleration appliance. For embodiments in which theremote machine 30 is an application acceleration appliance, the remotemachine 30 may provide functionality including firewall functionality,application firewall functionality, or load balancing functionality. Insome embodiments, the remote machine 30 comprises an appliance such asone of the line of appliances manufactured by the Citrix ApplicationNetworking Group, of San Jose, Calif. or Silver Peak Systems, Inc., ofMountain View, Calif., or of Riverbed Technology, Inc., of SanFrancisco, Calif., or of F5 Networks, Inc., of Seattle, Wash., or ofJuniper Networks, Inc., of Sunnyvale, Calif.

In some embodiments, a remote machine 30 comprises a remoteauthentication dial-in user service, referred to as a RADIUS server. Inother embodiments, remote machines 30 may have the capacity to functionas a master network information node monitoring resource usage of othermachines in the farm 38. In still other embodiments, a remote machine 30may provide an Active Directory. Remote machines 30 may be referred toas execution machines, intermediate machines, broker machines,intermediate broker machines, or worker machines.

In one embodiment, remote machines 30 in the machine farm 38 may bestored in high-density racking systems, along with associated storagesystems, and located in an enterprise data center. In this embodiment,consolidating the machines in this way may improve system manageability,data security, the physical security of the system, and systemperformance by locating machines and high performance storage systems onlocalized high performance networks. Centralizing the machines andstorage systems and coupling them with advanced system management toolsallows more efficient use of machine resources.

The client machines 10 may also be referred to as endpoints, clientnodes, clients, or local machines. In some embodiments, the clientmachines 10 have the capacity to function as both client machinesseeking access to resources and as remote machines 30 providing accessto remotely hosted resources for other client machines 10. In someembodiments, remote machines 30 may request access to remotely-hostedresources. In one of these embodiments, the remote machines 30 may bereferred to as client machines 10.

In one embodiment, the client machine 10 communicates directly with oneof the client machines 30 in a machine farm 38. In another embodiment,the client machine 10 executes an application to communicate with theremote machine 30 in a machine farm 38. In yet another embodiment, theclient machine 10 communicates with one of the remote machines 30 via agateway, such as an application gateway. In some embodiments, the clientmachine 10 communicates with the remote machine 30 in the machine farm38 over a communications link 150. Over the communications link 150, theclient machine 10 can, for example, request access to or execution ofvarious resources provided by remote machines 30, such as applications,computing environments, virtual machines, or hypervisors hosted by orexecuting on the remote machines 30, 30′, 30″, and 30′″ in the machinefarm 38. The client machine 10, 10′ receives for display output of theresults of execution of the resource or output of interaction betweenthe client machine 10 and the applications or computing environmentsprovided by the remote machines 30. In another of these embodiments,over the communications link 150, the client machine 10 can receive theoutput of applications executing in one or more virtual machines on aremote machine 30, 30′, 30″, and 30′″ in the machine farm 38.

The communications link 150 may be synchronous or asynchronous and maybe a LAN connection, MAN connection, or a WAN connection. Additionally,communications link 150 may be a wireless link, such as an infraredchannel or satellite band. The communications link 150 may use atransport layer protocol such as TCP/IP or any application layerprotocol, such as the Hypertext Transfer Protocol (HTTP), ExtensibleMarkup Language (XML), Independent Computing Architecture Protocol (ICA)manufactured by Citrix Systems, Inc. of Ft. Lauderdale, Fla., or theRemote Desktop Protocol manufactured by the Microsoft Corporation ofRedmond, Wash. In one embodiment, the communications link 150 uses aWi-Fi protocol. In still another embodiment, the communications link 150uses a mobile internet protocol.

The communications link 150 may provide communications functionalitythrough a variety of connections including standard telephone lines, LANor WAN links (e.g., T1, T3, 56 kb, X.25, SNA, DECNET), broadbandconnections (ISDN, Frame Relay, ATM, Gigabit Ethernet,Ethernet-over-SONET), and wireless connections or any combinationthereof. Connections can be established using a variety of communicationprotocols (e.g., TCP/IP, IPX, SPX, NetBIOS, Ethernet, ARCNET, SONET,SDH, Fiber Distributed Data Interface (FDDI), RS232, IEEE 802.11, IEEE802.11a, IEEE 802.11b, IEEE 802.11g, CDMA, GSM, WiMax and directasynchronous connections). In one embodiment, the remote machine 30 andthe client machine 10 communicate via any type and/or form of gateway ortunneling protocol such as Secure Socket Layer (SSL) or Transport LayerSecurity (TLS), or the Citrix Gateway Protocol manufactured by CitrixSystems, Inc. of Ft. Lauderdale, Fla. The computer system 100 mayinclude a network interface comprising a built-in network adapter,network interface card, PCMCIA network card, card bus network adapter,wireless network adapter, USB network adapter, modem or any other devicesuitable for interfacing the computer system 100 to any type of networkcapable of communication and performing the operations described herein.

The computer system 100 may support installation devices, such as afloppy disk drive for receiving floppy disks such as 3.5-inch, 5.25-inchdisks or ZIP disks, a CD-ROM drive, a CD-R/RW drive, a DVD-ROM drive,network interface card, tape drives of various formats, USB device,hard-drive or any other device suitable for installing software,programs, data or files, such as any software, or portion thereof.

The computer system 100 may also include a storage device of any typeand form for storing an operating system and other related software, andfor storing application software programs. In one embodiment, thestorage device includes one or more hard disk drives or redundant arraysof independent disks. In other embodiments, the storage device comprisesany type and form of portable storage medium or device, such as acompact flash card, a micro hard drive or pocket drive, embedded flashstorage, or USB storage drive. Portable storage devices may be generallyreferred to by a variety of names, including but not limited to, fingerdrive, flash disk, flash drive, flash memory drive, jump drive, jumpstick, keychain drive, keydrive, memory key, mobile drive, pen drive,thumb drive, thumb key, vault drive, USB drive, or USB stick.Optionally, any of the installation devices or mediums could alsoprovide a storage medium or device.

In some embodiments, the client machine 10 includes a client agent whichmay be, for example, implemented as a software program and/or as ahardware device, such as, for example, an ASIC or an FPGA. An example ofa client agent with a user interface is a Web Browser (e.g., INTERNETEXPLORER manufactured by Microsoft Corp. of Redmond, Wash. or SAFARI,manufactured by Apple Computer of Cupertino, Calif.). The client agentcan use any type of protocol, such as a remote display protocol, and itcan be, for example, an HTTP client agent, an FTP client agent, an Oscarclient agent, a Telnet client agent, an Independent ComputingArchitecture (ICA) client agent manufactured by Citrix Systems, Inc. ofFort Lauderdale, Fla., or a Remote Desktop Protocol (RDP) client agentmanufactured by Microsoft Corporation of Redmond, Wash. In someembodiments, the client agent is configured to connect to the remotemachine 30. In other embodiments (not shown), the client machine 10includes a plurality of client agents, each of which may communicatewith a remote machine 30, respectively.

In many embodiments, the remote machines 30, and the client machines 10,are provided as computers or computer servers, of the sort manufacturedby Apple Computer, Inc., of Cupertino, Calif., International BusinessMachines of White Plains, N.Y., Hewlett-Packard Corporation of PaloAlto, Calif. or the Dell Corporation of Round Rock, Tex. In someembodiments, the remote machines 30 may be blade servers, servers,workstation blades or personal computers executing hypervisors emulatinghardware required for virtual machines providing access to computingenvironments. In these embodiments, a single physical machine mayprovide multiple computing environments.

FIGS. 1A and 1B depict block diagrams of typical computer architecturesuseful in those embodiments as the remote machine 30, or the clientmachine 10. As shown in FIGS. 1A and 1B, each computer 100 includes acentral processing unit 102, and a main memory unit 104. Each computer100 may also include other optional elements, such as one or moreinput/output devices 130 a-130 n (generally referred to using referencenumeral 130), and a cache memory 140 in communication with the centralprocessing unit 102.

The central processing unit 102 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 104. Inmany embodiments, the central processing unit is provided by amicroprocessor unit, such as those manufactured by Intel Corporation ofMountain View, Calif.; those manufactured by Motorola Corporation ofSchaumburg, Ill.; those manufactured by International Business Machinesof White Plains, N.Y.; or those manufactured by Advanced Micro Devicesof Sunnyvale, Calif.

Main memory unit 104 may be one or more memory chips capable of storingdata and allowing any storage location to be directly accessed by themicroprocessor 102, such as Static random access memory (SRAM), BurstSRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM),Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended DataOutput RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), BurstExtended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM),synchronous DRAM (SDRAM), JEDEC SRAM, PC100 SDRAM, Double Data RateSDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM),Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM).

In the embodiment shown in FIG. 1A, the processor 102 communicates withmain memory 104 via a system bus 120 (described in more detail below).FIG. 1B depicts an embodiment of a computer system 100 in which theprocessor communicates directly with main memory 104 via a memory port.For example, in FIG. 1B, the main memory 104 may be DRDRAM.

FIG. 1A and FIG. 1B depict embodiments in which the main processor 102communicates directly with cache memory 140 via a secondary bus,sometimes referred to as a “backside” bus. In other embodiments, themain processor 102 communicates with cache memory 140 using the systembus 120. Cache memory 140 typically has a faster response time than mainmemory 104 and is typically provided by SRAM, BSRAM, or EDRAM.

In the embodiment shown in FIG. 1A, the processor 102 communicates withvarious I/O devices 130 via a local system bus 120. Various buses may beused to connect the central processing unit 102 to the I/O devices 130,including a VESA VL bus, an ISA bus, an EISA bus, a MicroChannelArchitecture (MCA) bus, a PCI bus, a PCI-X bus, a PCI-Express bus, or aNuBus. For embodiments in which the I/O device is a video display, theprocessor 102 may use an Advanced Graphics Port (AGP) to communicatewith the display. FIG. 1B depicts an embodiment of a computer system 100in which the main processor 102 communicates directly with I/O device130 b via HyperTransport, Rapid I/O, or InfiniBand. FIG. 1B also depictsan embodiment in which local busses and direct communication are mixed:the processor 102 communicates with I/O device 130 a using a localinterconnect bus while communicating with I/O device 130 b directly.

A wide variety of I/O devices 130 may be present in the computer system100. Input devices include keyboards, mice, trackpads, trackballs,microphones, and drawing tablets. Output devices include video displays,speakers, inkjet printers, laser printers, and dye-sublimation printers.An I/O device may also provide mass storage for the computer system 100such as a hard disk drive, a floppy disk drive for receiving floppydisks such as 3.5-inch, 5.25-inch disks or ZIP disks, a CD-ROM drive, aCD-R/RW drive, a DVD-ROM drive, DVD-RW drive, DVD+RW drive,, tape drivesof various formats, and USB storage devices such as the USB Flash Driveline of devices manufactured by Twintech Industry, Inc. of Los Alamitos,Calif., and the iPod Shuffle line of devices manufactured by AppleComputer, Inc., of Cupertino, Calif.

In some embodiments, the client machine 10 may comprise or be connectedto multiple display devices, which each may be of the same or differenttype and/or form. As such, any of the I/O devices 130 a-130 n maycomprise a display device or any type and/or form of suitable hardware,software, or combination of hardware and software to support, enable orprovide for the connection and use of multiple display devices by theclient machine 10. For example, the client machine 10 may include anytype and/or form of video adapter, video card, driver, and/or library tointerface, communicate, connect or otherwise use the display devices. Inone embodiment, a video adapter may comprise multiple connectors tointerface to multiple display devices. In other embodiments, the clientmachine 10 may include multiple video adapters, with each video adapterconnected to one or more of the display devices. In some embodiments,any portion of the operating system of the client machine 10 may beconfigured for using multiple displays. In other embodiments, one ormore of the display devices may be provided by one or more othercomputing devices, such as remote machine 30 connected to the clientmachine 10, for example, via a network. These embodiments may includeany type of software designed and constructed to use another computer'sdisplay device as a second display device for the client machine 10. Oneordinarily skilled in the art will recognize and appreciate the variousways and embodiments that a client machine 10 may be configured to havemultiple display devices.

In further embodiments, an I/O device 130 may be a bridge between thesystem bus 120 and an external communication bus, such as a USB bus, anApple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWirebus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a GigabitEthernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a SuperHIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or aSerial Attached small computer system interface bus.

General-purpose computers of the sort depicted in FIG. 1A and FIG. 1Btypically operate under the control of operating systems which controlscheduling of tasks and access to system resources. In some embodiments,the computers operate under control of hypervisors, which representvirtualized views of physical hardware as one or more virtual machines.Operating systems may execute in these virtual machines to control thevirtual machine in a manner analogous to the way a native operatingsystem controls a physical machine. Typical operating systems include:the MICROSOFT WINDOWS family of operating systems, manufactured byMicrosoft Corp. of Redmond, Wash.; the MacOS family of operatingsystems, manufactured by Apple Computer of Cupertino, Calif.; OS/2,manufactured by International Business Machines of Armonk, N.Y.; andLinux, a freely-available operating system distributed by Caldera Corp.of Salt Lake City, Utah, among others.

The client machines 10 and 20 may be any personal computer (e.g., aMacintosh computer or a computer based on processors manufactured byIntel Corporation of Mountain View, Calif.), Windows-based terminal,Network Computer, wireless device, information appliance, RISC Power PC,X-device, workstation, mini computer, main frame computer, personaldigital assistant, television set-top box, living room media center,gaming console, mobile gaming device, NetPC's, thin client, or othercomputing device that has a windows-based desktop and sufficientpersistent storage for executing a small, display presentation program.The display presentation program uses commands and data sent to itacross communication channels to render a graphical display.Windows-oriented platforms supported by the client machines 10 and 20can include, without limitation, WINDOWS 3.x, WINDOWS 95, WINDOWS 98,WINDOWS NT 3.51, WINDOWS NT 4.0, WINDOWS 2000, Windows 2003, WINDOWS CE,Windows XP, Windows Vista, MAC/OS, Java, Linux, and UNIX. The clientmachines 10 can include a visual display device (e.g., a computermonitor), a data entry device (e.g., a keyboard), persistent or volatilestorage (e.g., computer memory) for storing downloaded applicationprograms, a processor, and a mouse. Execution of a small, displaypresentation program allows the client machines 10 to participate in adistributed computer system model (i.e., a server-based computingmodel).

In other embodiments, the general-purpose computers of the sort depictedin FIG. 1A and FIG. 1B may have different processors, operating systems,and input devices consistent with the device and in accordance withembodiments further described herein. The computer system 100 can be anyworkstation, desktop computer, laptop or notebook computer, server,handheld computer, mobile telephone or other portable telecommunicationdevice, media playing device, a gaming system, or any other type and/orform of computing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. For example, thecomputer system 100 may comprise a device of the IPOD family of devicesmanufactured by Apple Computer of Cupertino, Calif., a PLAYSTATION 2,PLAYSTATION 3, or PERSONAL PLAYSTATION PORTABLE (PSP) devicemanufactured by the Sony Corporation of Tokyo, Japan, a NINTENDO DS,NINTENDO GAMEBOY, NINTENDO GAMEBOY ADVANCED or NINTENDO REVOLUTIONdevice manufactured by Nintendo Co., Ltd., of Kyoto, Japan, or an XBOXor XBOX 360™ device manufactured by the Microsoft Corporation ofRedmond, Wash.

For embodiments in which a client machine 10 is a mobile device, thedevice may be a JAVA-enabled cellular telephone, such as thosemanufactured by Motorola Corp. of Schaumburg, Ill., those manufacturedby Kyocera of Kyoto, Japan, or those manufactured by Samsung ElectronicsCo., Ltd., of Seoul, Korea. In other embodiments in which the clientmachine 10 is mobile, it may be a personal digital assistant (PDA)operating under control of the PalmOS operating system, such as thedevices manufactured by palmOne, Inc. of Milpitas, Calif. In furtherembodiments, the client machine 10 may be a personal digital assistant(PDA) operating under control of the PocketPC operating system, such asthe iPAQ devices manufactured by Hewlett-Packard Corporation of PaloAlto, Calif., the devices manufactured by ViewSonic of Walnut, Calif.,or the devices manufactured by Toshiba America, Inc. of New York, N.Y.In still other embodiments, the client machine 10 is a combinationPDA/telephone device such as the Treo devices manufactured by palmOne,Inc. of Milpitas, Calif. In still further embodiments, the clientmachine 10 is a cellular telephone that operates under control of thePocketPC operating system, such as those manufactured by Motorola Corp.

In some embodiments, a client machine 10 communicates with a remotemachine 30 to determine an enumeration of resources available to theclient machine 10 or to a user of the client machine 10. Resources mayinclude, without limitation, computing environments, applications,documents, and hardware resources. In another of these embodiments, theremote machine 30 provides the client machine 10 with addressinformation associated with a remote machine 30′ hosting a resourceidentified by the enumeration of resources. In still another of theseembodiments, the client machine 10 communicates with the remote machine30′ to access the identified resource. In one embodiment, the clientmachine 10 executes a resource neighborhood application to communicatewith the remote machines 30 and 30′. In some embodiments, each of theremote machines 30 provides the functionality required to identify andprovide address information associated with a remote machine 30′ hostinga requested resource.

Referring now to FIG. 2A, a block diagram depicts one embodiment of asystem for providing access to a resource. In brief overview, a requestto enumerate computing resources is transmitted from a client machine 10(step 202). In some embodiments, the request includes an identificationof a user of the client machine 10. An enumeration of a plurality ofresources available to the user of the requesting machine is provided bythe remote machine (step 204). The client machine 10 transmits a requestfor access to a particular resource included in the enumeration (step206).

Still referring to FIG. 2A, and in more detail, the transmitted requestis a request for an enumeration of computing environments available tothe client machine 10. In another embodiment, the request is a requestfor an enumeration of computing environments supporting a particularapplication requested for execution by the client machine 10. In stillanother embodiment, the request is a request for access to a computingenvironment supported by a particular plurality of hardware resources.

In some embodiments, information associated with the client machine 10or with a user of the client machine 10 is received with the request. Inone of these embodiments, credentials associated with the user, or witha user of the client machine 10, are received. In one embodiment, theremote machine 30 receives a request for an enumeration of availablecomputing environments from the client machine 10 with the informationassociated with the client machine 10, 10′ or the user of the clientmachine 10. In another embodiment, the remote machine 30 receives atransmission from a policy engine including the information. In stillanother embodiment, the remote machine 30 receives a transmission from acollection agent including the information. In yet another embodiment,the remote machine 30 comprises a component receiving requests andassociated information.

In some embodiments, a remote machine 30 functioning as a web serverreceives communications from the client machine 10, 10′. In one of theseembodiments, the web server forwards the communications to a remotemachine 30′. In one of these embodiments, the web server forwards thecommunications to a service on the remote machine 30′. In another ofthese embodiments where communications from the client machine 10, 10′are routed to a remote machine 30′ by the web server, the remote machine30 may be selected responsive to an Internet Protocol (IP) address ofthe client machine 10.

In some embodiments, the user provides credentials to the remote machine30 via a graphical user interface presented to the client machine 10,10′ by the remote machine 30. In other embodiments, a remote machine30′″ having the functionality of a web server provides the graphicaluser interface to the client machine 10. In still other embodiments, acollection agent transmitted to the client machine 10, 10′ by the remotemachine 30 gathers the credentials from the client machine 10.

In some embodiments, collected data regarding available resources isaccessed. In some of these embodiments, collected data regardingcomputing environments is accessed. In some of these embodiments, theaccessed data includes an indication of a virtual machine providingaccess to one of the computing environments. In one of theseembodiments, the accessed data includes an indication of a location ofthe virtual machine. In other embodiments, the accessed data concerningcomputing environments includes an indication of a plurality of hardwareresources required to support the computing environments. In still otherembodiments, the accessed data concerning computing environmentsincludes an indication of a user or type of user authorized to accessthe computing environments. In yet other embodiments, the accessed datais provided responsive to a request for identification of a computingenvironment providing access to an application program.

In some embodiments, the collected data is stored on a server, such as aremote machine 30. In other embodiments, the server is in communicationwith a database storing the collected data. In still other embodiments,the server collects the data from a plurality of machines 30 in amachine farm 38. In one of these embodiments, the data is received fromat least one server responsive to a request for the informationconcerning the computing environments. In another of these embodiments,the server collects the data from a hypervisor executing on a machine30′ in the machine farm 38. In still another of these embodiments, theserver collects the data from a management component residing in a guestoperating system provided by a virtual machine launched into ahypervisor executing on a machine 30′ in the machine farm 38.

In some embodiments, the data is collected by an intermediate, brokeringmachine. In one of these embodiments, the brokering machine maintains adatabase of a status of at least one computing environments and collectsinformation from at least one machine providing access to at least onecomputing environments. In another of these embodiments, the brokeringmachine collects information from a virtual machine service componentresiding in a virtual machine providing the computing environments. Instill another of these embodiments, the brokering machine collectsinformation from a virtual machine providing management functionalityfor a virtual machine providing a computing environment. In yet anotherof these embodiments, the brokering machine collects information from ahypervisor on which an executing virtual machine provides a computingenvironment. In other embodiments, the brokering machine comprises amachine 30 including a brokering module.

In some embodiments, a determination is made for each availablecomputing environment as to whether that computing environment isavailable to a user of the client system. In other embodiments, data isgathered about the client system and a data set is generated from thegathered information. In one of these embodiments, the accessed data istransmitted to the client system with an indication to the clientsystem, made responsive to the generated data set, of each computingenvironment available to the client system. In another of theseembodiments, the accessed data is transmitted to the client systemindicating to the client system, responsive to the application of apolicy to the generated data set, each computing environment availableto the client system. In still another of these embodiments, theindication includes at least one method of access available to the userseeking access to the computing environment. In yet another of theseembodiments, the indication includes at least one type of actionassociated with the computing environment which may be taken by, or onbehalf of, the user of the client system.

An enumeration of a plurality of resources available to the clientmachine 10 is provided (step 204). In one embodiment, the enumeration isprovided responsive to an application of a policy to receivedinformation associated with the user of the client machine 10 or theremote machine 30. In another embodiment, the enumeration is providedresponsive to a request from the user for a particular type of computingenvironment. In still another embodiment, the enumeration is providedresponsive to a request from the user for computing environmentsproviding access to a type of application program. In yet anotherembodiment, the enumeration is provided responsive to a request from theuser for computing environments supported by a specified plurality ofhardware resources.

In some embodiments, an indication is transmitted to the client machine10 of a plurality of computing environments available to a user of theclient machine 10. In one of these embodiments, the indication isgenerated responsive to accessing collected data associated with theplurality of computing environments. In another of these embodiments,the accessed data is transmitted to the client machine 10 with anenumeration of computing environments available to the client machine10. In some embodiments, a determination is made, for each storedcomputing environment, as to whether that computing environment isavailable to the client machine 10. In one embodiment, the collectedinformation is transmitted to the client machine 10, the transmittedinformation displayable at the client machine 10 as icons in a graphicaluser interface window representing computing environments available tothe client system. In another embodiment, the collected information istransmitted to the client machine 10, the transmitted informationdisplayable at the client machine 10 as icons in a graphical userinterface window representing computing environments unavailable to theclient machine 10.

In some embodiments, an enumeration of available computing environmentsis presented to a user of the client machine 10. In other embodiments,an enumeration of applications is presented to a user of the clientmachine 10. In one of these embodiments, a physical machine providesaccess to an enumerated application. In another of these embodiments, avirtual machine provides access to an enumerated application. In stillanother of these embodiments, a virtual machine provides access to acomputing environment from which a user of the client machine 10 mayaccess the application. In still other embodiments, an enumeration ofstandard operating environments (such as a guest operating systempre-configured with a plurality of application programs) is provided tothe user of the client machine 10.

In some embodiments, the enumeration of available resources includes anenumeration of a plurality of actions associated with a requestedresource. In one of these embodiments, the enumeration of the pluralityof actions enables the user to request execution of a computingenvironment. In another of these embodiments, the enumeration of theplurality of actions enables the user to request cloning of a computingenvironment. In still another of these embodiments, the enumeration ofthe plurality of actions enables the user to request shutdown of acomputing environment. In yet another of these embodiments, theenumeration of the plurality of actions enables the user to request thata computing environment be rebooted. In some embodiments, theenumeration of the plurality of actions enables the user to request thata snapshot be taken of an existing state of a computing environment. Inother embodiments, the enumeration of the plurality of actions enablesthe user to request that a previous snapshot of a computing environmentbe provided.

A request is transmitted for access to a particular resource (step 206).In one embodiment, a user of the client machine 10 requests a resourceresponsive to a received enumeration of available resources. In anotherembodiment, the user requests a resource independent of a receivedenumeration. In some embodiments, the user requests a resource byselecting a graphical representation of the resource presented on theclient machine 10 by a client agent. In other embodiments, the userrequests a resource by selecting a graphical or textual representationof the resource presented to the user on a web server or other remotemachine 30′″.

In some embodiments, the user requests an action associated with aresource. In one of these embodiments, the user requests execution ofthe resource. In another of these embodiments, the user requeststermination of the resource. In still another of these embodiments, theuser requests transmission of the resource, including transmissionacross an application streaming session. In yet another of theseembodiments, the user requests that a resource be shutdown. In otherembodiments, a request to execute an application is received from theclient machine 10, the requested application requiring one of thecomputing environments. In still other embodiments, a request to accessa file is received from the client machine 10, the requested filerequiring execution within one of the computing environments.

Still referring to FIG. 2A, a remote machine 30 launches the ResourceNeighborhood (RN) application and presents results of the RN applicationto the client machine 10. The remote machine 30 can launch the RNapplication 241 in response to a request 202 by the client machine 10for an enumeration of available resources. The remote machine 30provides an enumeration of available resources to the client machine 10(step 204). The client machine 10 and remote machine 30′ establish aconnection (arrows 245 and 246). By this connection, the remote machine30′ can transfer the executable code of the particular application tothe client machine 10, when the client machine 10 and remote machine 30′are operating according to the client-based computing model.Alternatively, the remote machine 30′ can execute the particularapplication and transfer the graphical user interface to the clientmachine 10, when the client machine 10 and remote machine 30′ areoperating according to the server-based computing model. In someembodiments the remote machine 30′ can execute the Resource Neighborhoodapplication 241 and push the results back to the client machine 10 sothat when the client machine 10 requests the Resource Neighborhoodapplication, the Resource Neighborhood results are already available atthe client machine 10.

FIG. 2B shows another embodiment of a system in which the client machine10 initiates execution of the Resource Neighborhood application 241 anda remote machine 30 presents the results of the RN application 241 tothe client machine 10. The client machine 10 launches the ResourceNeighborhood application (e.g., by clicking on a Resource Neighborhoodicon representing the application 241). In response, the client machine10 directs a request 202 for the Resource Neighborhood application tothe remote machine 30. The remote machine 30 can execute the ResourceNeighborhood application 241, if the application is on the remotemachine 30, and return the results to the client machine 10.Alternatively, the remote machine 30 can indicate (arrow 204) to theclient machine 10 that the Resource Neighborhood application 241 isavailable on another remote machine, in this example remote machine 30′.The client machine 10 and remote machine 30′ establish a connection(arrows 206 and 210) by which the client machine 10 requests executionof the Resource Neighborhood application 241. The remote machine 30′ canexecute the application 241 and transfer the results (i.e., thegraphical user interface any audio output etc.) to the client machine10.

FIG. 2C shows another embodiment of a system in which a client machine10 initiates execution of the Resource Neighborhood application 241, inthis example via the World Wide Web. A client machine 10 executes a webbrowser application 280, such as NETSCAPE NAVIGATOR, manufactured byNetscape Communications, Inc. of Mountain View, Calif., INTERNETEXPLORER, manufactured by Microsoft Corporation of Redmond, Wash., orSAFARI, manufactured by Apple Computer of Cupertino, Calif.

The client machine 10, via the web browser 280, transmits a request 282to access a Uniform Resource Locator (URL) address corresponding to anHTML page residing on remote machine 10. In some embodiments, the firstHTML page returned 284 to the client machine 10 by the remote machine 30is an authentication page that seeks to identify the client machine 10or the user of the client machine 10.

The authentication page allows the client machine 10 to transmit usercredentials, via the web browser 280, to the remote machine 30 forauthentication. Transmitted user credentials are verified either by theremote machine 30 or by another remote machine 30 in the farm 38. Thisallows a security domain to be projected onto the remote machine 30. Forexample, if the remote machine 30 runs the WINDOWS NT operating system,manufactured by Microsoft Corporation of Redmond, Wash., and theauthenticating machine runs the UNIX operating system, the UNIX securitydomain may be said to have been projected onto the remote machine 30.User credentials may be transmitted “in the clear,” or they may beencrypted. For example, user credentials may be transmitted via a SecureSocket Layer (SSL) connection, which encrypts data using algorithms suchas the RC4 algorithm, manufactured by RSA Security Inc. of Bedford,Mass.

In some embodiments, an access control decision is made based onreceived information about the user resources available to the user ofthe client system are identified responsive to the access controldecision. In other embodiments, a policy is applied to the receivedinformation about the user. The remote machine 30 may verify the usercredentials received from the client machine 10. Alternatively, theremote machine 30 may pass the user credentials to another remotemachine for authentication. In this embodiment, the authenticatingserver may be in a different domain from the remote machine 30.Authenticated user credentials of the client machine 10 may be stored atthe client machine 10 in a per-session cookie, in fields that are notdisplayed by the web browser 280, or in any other manner common inmaintenance of web pages. In some embodiments, a machine farm 38 withwhich the remote machine 30 is associated may allow guest users, i.e.,users that do not have assigned user credentials, to access resourceshosted by the farm 38. In these embodiments, the authentication page mayprovide a mechanism for allowing a client machine 10 to identify that itis a guest user, such as a button or menu selection. In other of theseembodiments, the remote machine 30 may omit the authentication pageentirely.

Still referring to FIG. 2C, once the client machine 10 is authenticatedby the remote machine 30, the remote machine prepares and transmits tothe client machine 10 an HTML page 288 that includes a ResourceNeighborhood window 258 in which appears graphical icons 257, 257′representing resources to which the client machine 10 has access. A userof client machine 10 requests access to a resource represented by icon257 by clicking that icon 257.

FIG. 3A shows one embodiment of a process of communication among theclient machine 10 and multiple remote machines 30, 30′. In theembodiment shown in FIG. 3A, the client machine 10 has an activeconnection 372 with the remote machine 30′. The client machine 10 andremote machine 30′ can use the active connection 372 to exchangeinformation regarding the status or execution of a first resource. Usercredentials may be stored at the client machine 10. Such storage of theuser credentials can be in cache memory or persistent storage.

In this embodiment, the Resource Neighborhood application (not shown onFIG. 3A) runs on the client machine 10. The client machine display has aResource Neighborhood window 258 in which appears a graphical icon 257representing a second resource. A user of the client machine 10 canaccess the second resource by double-clicking the icon 257 with themouse. The request passes to the remote machine 30 via connection 359.The remote machine 30 indicates to the client machine 10 via connection359 that the sought-after resource is available on remote machine 30′.The client machine 10 signals the remote machine 30′ to establish asecond connection 370. The remote machine 30′ requests the usercredentials from the client machine 10 to authenticate access to thesecond resource. Upon a successful authentication, the client machine 10and remote machine 30′ establish the second connection 370 and exchangeinformation regarding status of or execution of the second resource. Insome embodiments, the remote machine does not request user credentialsto establish the second connection 370. In these embodiments, the remotemachine 30′ may use the credentials supplied by the user of clientmachine 10 to establish the connection 372 to also establish the secondconnection 370. Accordingly, the client machine 10 and the remotemachine 30′ communicate with each other over multiple connections.

FIG. 3B shows one embodiment of a system of communication among theclient machine 10, master remote machine 30, and servers 32, 34, and 36.The client machine 10 has an active connection 373 with the remotemachine 32. The client machine 10 and remote machine 32 can use theactive connection 373 to exchange information regarding the status of orexecution of a first resource. User credentials may be stored at theremote machine 32 in cache memory or in persistent storage.

In this embodiment, the Resource Neighborhood application runs on theremote machine 32. The remote machine 32 includes software providing aserver-based client engine 62, enabling the remote machine 32 to operatein the capacity of the client machine 10. The client machine 10 displayhas a Resource Neighborhood window 258 in which appear graphical icons357, 357′ representing a second resource and a third resource,respectively. A user of the client machine 10 can access the secondresource by double-clicking the icon 357. The request to launch thesecond resource passes to the remote machine 32 via active connection373, and the remote machine 32 forwards the request to the master remotemachine 30 (arrow 365).

The master remote machine 30 indicates (arrow 365) to the remote machine32 that the sought-after resource is available on server 34. The remotemachine 32 contacts the server 34 to establish a connection 366. Toauthenticate access to the application, the server 34 obtains the usercredentials of the client machine 10 from the remote machine 32. Theremote machine 32 and server 34 establish the connection (arrow 366) bywhich the remote machine 32 requests access to the second resource andthe server 34 returns the results to the remote machine 32. The remotemachine 32 forwards the results to the client machine 10, where theresults are displayed. Accordingly, the information exchanged betweenthe client machine 10 and the server 34 “passes through” the remotemachine 32.

Similarly, the client machine 10 can launch the third resource bydouble-clicking the icon 357′. The request to launch the third resourcepasses to the remote machine 32. The remote machine 32 forwards therequest to the master remote machine 30. In this example, the masterremote machine 30 indicates that the server 36 can be used to access thethird resource.

The remote machine 32 and the server 36 establish a connection (arrow374) by which the remote machine 32 requests access to the thirdresource, and the server 36 returns the results to the remote machine32. To permit access to the third resource, the server 36 canauthenticate the user credentials of the user of the client machine 10,which are obtained from the remote machine 32. The remote machine 32forwards the results to the client machine 10 where the results aredisplayed. Accordingly, the results of accessing the third resource passbetween the client machine 10 and the server 36 through the remotemachine 32.

FIG. 3C shows another embodiment of a system of communication among theclient machine 10, a master remote machine 30, and servers 32 and 34.The client machine 10 has an active connection 376 with server 32. Theclient machine 10 and server 32 can use the active connection 376 toexchange information regarding the access to a first resource. Theclient machine 10 can store user credentials in cache memory or inpersistent storage.

In this embodiment, the Resource Neighborhood application runs on theserver 32. The client machine 10 display has a Resource Neighborhoodwindow 258 in which appears a graphical icon 257 representing a secondresource. A user of the client machine 10 can access the second resourceby double-clicking the icon 257. The request to access the secondresource passes to the server 32. The server 32 responds (i.e., “callsback”) to the client machine 10 by returning resource-relatedinformation such as the name of the resource and capabilities needed bythe client machine 10 to access the second application.

With the information provided by the server 32, the client machine 10then communicates with the master remote machine 30 via connection 377to determine the server for accessing the second resource. In thisexample, that server is server 34. The client machine 10 thenestablishes a connection 378 to the server 34. Server 34 requests theuser credentials from the client machine 10 to authenticate the user ofthe client machine 10. The client machine 10 accesses the secondresource on the server 34, and the server 34 returns the results to theclient machine 10 via the established connection 378. Accordingly, theclient machine 10 can have multiple active connections between themultiple servers.

FIG. 3D shows one embodiment of a system of communication between theclient machine 10, a remote machine 30 that in this example acts as aweb server, and a second remote machine 30′. The client machine 10authenticates itself to the remote machine 30 as described above inconnection with FIG. 2C. In one embodiment, the remote machine 30accesses an output display template 390, such as an SGML, HTML or XMLfile, to use as a base for constructing the Resource Neighborhood windowto transmit to the client machine 10. The Resource Neighborhood windowmay display an enumeration of resources available to the client. Theenumeration of resources may include an enumeration of availableapplication programs or computing environments. The template may bestored in volatile or persistent memory associated with the server 30 orit may be stored in mass memory 392, such as a disk drive or opticaldevice, as shown in FIG. 3D.

In this embodiment, the template 390 is a standard SGML, HTML, or XMLdocument containing Resource Neighborhood-specific tags that arereplaced with dynamic information. The tags indicate to the server 30where in the output display to insert information corresponding toavailable resources, such as icon images. In one particular embodiment,the Resource Neighborhood-specific tags are embedded within commentsinside a file, allowing the file to remain compatible with standardinterpreters. In another embodiment, the Resource Neighborhood-specifictags are extensions of the markup language used as the base for thetemplate.

Examples of HTML tags that may be used in a template are set forth belowin Table 1: TABLE 1 Tag Description ControlField field value This tag isused to set the value of data that either persists between ResourceNeighborhood web pages, is set by the user, or is used to help in crosspage navigation, such as user name, domain, password, template, andresource. DrawResourceNeighborhood This tag is used to draw a ResourceNeighborhood display at this location in an output display. ResourceNameThis tag is replaced by the name of the published resource in thecurrent context. WindowType This tag is replaced by the window type ofthe published resource in the current context. WindowHeight This tag isreplaced by the window height of the published resource in the currentcontext. WindowWidth This tag is replaced by the window width of thepublished resource in the current context. WindowScale This tag isreplaced by the window scale of the published resource in the currentcontext. WindowColors This tag is replaced by the color depth of thepublished resource in the current context. SoundType This tag isreplaced by the sound setting of the published resource in the currentcontext. VideoType This tag is replaced by the video setting of thepublished resource in the current context. EncryptionLevel This tag isreplaced by the encryption level of the published resource in thecurrent context. Icon This tag is replaced by the icon of the publishedresource in the current context.

Other tags can be provided to set control fields and to provideconditional processing relating to the Resource Neighborhoodapplication.

In one embodiment, the template is constructed dynamically using, forexample, COLD FUSION, manufactured by Allaire Corp. of Cambridge, Mass.or ACTIVE SERVER PAGES manufactured by Microsoft Corporation of Redmond,Wash. Alternatively, the template may be static. The ResourceNeighborhood application parses the template, replacing ResourceNeighborhood-specific tags as noted above. Tags that are not ResourceNeighborhood-specific are left in the file to be parsed by the browserprogram 80 executing on the client 10.

In one embodiment, a template parser object is provided that accepts anHTML template as input, interprets Resource Neighborhood-specific tagspresent in the template, and outputs the original template with allResource Neighborhood tags replaced with appropriate text. The templateparser object can be passed a cookie, a URL query string, or a controlfield from a web server interface to provide the information with whichResource Neighborhood-specific tags should be replaced.

In some embodiments, a web server receives a request from the clientmachine 10 for an enumeration of available computing environments. Inone of these embodiments, the web server executes an application toaccess data regarding the computing environments. In another of theseembodiments, a page template is retrieved from a database. In still ofthese embodiments, a page is created, at the web server, describing adisplay of stored computing environment images available to the clientmachine 10 responsive to the collected information and the retrievedpage template, and the created page is transmitted to the client machine10, indicating to the client machine 10 each computing environmentavailable to the client machine 10. In some embodiments, computingenvironment images may comprise virtual machine images, resource images,screenshots of suspended virtual machines, and other images selected bya user or administrator for presentation to the user. In yet another ofthese embodiments, an output display is created indicating eachcomputing environment available to the client machine 10 andtransmitting the created output display to the client machine 10.

In some embodiments, an output display is created comprising a pageconstructed in a markup language, the output display indicating eachcomputing environment available to the client system and transmitted tothe client system.

In another embodiment, the Resource Neighborhood application allowsscripts to access information via an application programming interface.Scripts may be written in, for example, VBScript or Jscript. In thisembodiment, the scripting language is used to dynamically generate anoutput display using information returned by the application in responseto queries posed by the script. Once the output display is generated, itis transmitted to client machine 10 for display by the browser program80.

A user of the client machine 10 can access a resource by clicking anicon 257, 257′ displayed in the Resource Neighborhood web page. In someembodiments, each icon 257, 257′ is associated with an encoded URL thatspecifies: the location of the resource (i.e., on which remote machinesit is hosted or, alternatively, the address of a master remote machine,a gateway, or other remote machine 30); a launch command associated withthe resource; and a template identifying how the results of accessingthe resource should be displayed (i.e., in a window “embedded” in thebrowser or in a separate window). In some embodiments, the URL includesa file, or a reference to a file, that contains the informationnecessary for the client to create a connection to the remote machinehosting the resource. This file may be created by the ResourceNeighborhood application dynamically. The client machine 10 establishesa connection (arrow 394) with the remote machine 30′ identified ashosting the requested resource and exchanges information regardingaccess to the desired resource. In some embodiments, the connection 394is made using the Independent Computing Architecture (ICA) protocol,manufactured by Citrix Systems, Inc. of Fort Lauderdale, Fla. In otherembodiments, the connection is made using: the RDP protocol,manufactured by Microsoft Corp. of Redmond, Wash.; the X11 protocol; orthe Virtual Network Computing (VNC) protocol, manufactured by AT&T BellLabs. Thus, the client machine 10 may display the results of accessingthe resource in a window separate from the web browser 280, or it may“embed” application output within the web browser.

FIG. 3E depicts an embodiment in which a remote machine 30 acts as anintermediary for a machine farm 38 and comprises a broker module 310, atransmitter 312, a receiver 314, and a transceiver 316.

The broker module 310 accesses collected data regarding resources,including application programs, computing environments, and hardwareresources. In some embodiments, the broker module 310 accesses collecteddata regarding resources and determines for each resource whether thatresource image is available to a client machine 10. In some embodiments,the server further comprises a database storing the collected data. Inone of these embodiments, the broker module 310 determines for eachresource whether that resource image is available to a client machine 10based on the collected data. In other embodiments, the broker module 310receives user credentials and determines for each resource whether thatresource image is available to a client machine 10 based on the usercredentials and the collected data.

In some embodiments, the server further comprises an output displaycreation engine creating output displays indicating each resourceavailable to the client machine 10. In one of these environments, theoutput display creation engine creates a page describing a display ofthe resources available to a client system, the page created responsiveto the collected information and a page template.

The transmitter 312 transmits accessed data to the client machine 10indicating to the client machine 10 each resource determined to beavailable to the client machine 10. In some embodiments, the transmitteddata is displayable at the client system as icons in a graphical userinterface window representing resources available to the client system.In other embodiments, the transmitted data is displayable at the clientsystem as icons in a graphical user interface window representingresources unavailable to the client system. The receiver 314 receives arequest to access one of the available resources. In some embodiments,the receiver receives user credentials from the client machine 10. Inother embodiments, the receiver receives a request to access anapplication program available through one of the available resources,such as an available computing environment. In still other embodiments,a database storing the collected information and the service moduledetermines for each resource stored by the plurality of servers whetherthat resource image is available to a client machine 10 based on theuser credentials and the collected information. In yet otherembodiments, a determination is made as to an availability of resources,such as virtual machines or application servers, providing access to theavailable resources.

The transceiver 316 provides a connection between the client machine 10and a virtual machine providing the requested resource. In someembodiments, the transceiver 316 provides a connection between theclient machine 10 and a virtual machine providing the requested resourceand the transceiver 316 establishes a presentation-layer protocolconnection. In one of these embodiments, the transceiver 316 establishesan X11 or VNC connection. In another of these embodiments, thetransceiver 316 establishes an ICA connection. In still another of theseembodiments, the transceiver 316 establishes an RDP connection.

An intermediary machine of the sort just described may be used as anyone of the remote machine 30 described above in FIGS. 1-1B, 2A-2B, and3A-3D.

FIG. 4 illustrates one embodiment of program components for aclient-based implementation of the Resource Neighborhood application. Aclient-based implementation of the Resource Neighborhood application 416can be used in a network using either the server-based computing modelin which the servers execute the Resource Neighborhood application or ina client-based computing model in which the client machine 10 executesthe Resource Neighborhood application locally. The Resource Neighborhoodapplication includes a Resource Neighborhood Service (RNSVC) component444, a resource database component 448, a Resource NeighborhoodApplication Program Interface (RNAPI) component 452, a ResourceNeighborhood User Interface component 456, and a local cache 460.

The remote machine 30, for example, includes the service component(RNSVC) 444 and the resource authorization cache 448. The client machine10, which is a representative example of a client machine 10 that cansupport a client-based implementation of the Resource Neighborhoodapplication, includes the application program interface RNAPI 452, theuser interface user interface component 456, and the local cache 460components. The RNAPI 452 communicates with the user interface component456 and the local cache 460. The RNSVC 444 communicates with theresource authorization cache 448 and with the RNAPI 452 on the clientmachine 10 via communications link 462.

The communications link 462 can be established by, for example, usingthe ICA protocol, the RDP protocol, the X11 protocol, the VNC protocol,or any other suitable presentation-level protocol designed to run overindustry standard transport protocols, such as TCP/IP, IPX/SPX, NetBEUI,using industry-standard network protocols, such as ISDN, frame relay,and asynchronous transfer mode (ATM) and which provides for virtualchannels, which are session-oriented transmission connections that canbe used by application-layer code to issue commands for exchanging data.The communications link 462 may also be established by protocols thatsupport RPC or RPC-equivalents such as SOAP and HTTP. The communicationslink 462 may also be a communications link 150 as described above. Thevirtual channel commands are designed to be closely integrated with thefunctions of client machines. The ICA protocol can support the ResourceNeighborhood virtual channel.

The Resource Neighborhood virtual channel protocol can include fourgroups of commands:

(1) Initialization-related commands;

(2) Single authentication related commands that can be supported by eachclient machine wanting a copy of the user credentials;

(3) Resource data related commands for implementing the ResourceNeighborhood user interface; and

(4) Resource launch callback-related commands for running the userinterface on a remote machine.

The resource authorization cache 448 may be a cache of the authorizeduser and group information for all the public (i.e., published)resources in a machine farm 38 or in a group of trusted domains. Eachremote machine in a machine farm 38 can maintain its ownresource-related information in persistent storage and build up theresource authorization cache 448 in volatile storage. In anotherembodiment, all collected resource-related information in the resourceauthorization cache 448 can be stored in persistent storage and madeaccessible to each other server in the machine farm 38. The resourceauthorization cache 448 can be implemented in a proprietary format(e.g., as a linked list in memory) or using Novell's Directory Services(NDS) or any directory service adhering to the X.500 standard defined bythe International Telecommunication Union (ITU) for distributedelectronic directories. The resource authorization cache 448 may beimplemented as a standard relational database.

The resource authorization cache 448 includes a list of remote machines.Each remote machine in the list has an associated set of resources.Associated with each resource is resource-related information that caninclude the resource name, a list of remote machines, and client usersthat are authorized to use that resource. An overly-simplified exampleof the resource-related information maintained in the database isillustrated by the following Table 2. Users A and B are users of theclient machines 10, “n/a” indicates that a desired application programis hosted, but is not available to client machine users, and “-”indicates that the application program is not hosted. TABLE 2 RemoteCustomer Word Machine Name SpreadSheet Database Processor CalculatorServer 30 User A User B n/a — Server 32 User B n/a User A — Server 34 —— — User A User B

Table 2 shows: a list of servers 30, 32, 34; applications hosted by theservers (Spreadsheet, Customer Database, Word Processor, andCalculator); and those users who are authorized to use the applications.For example, the server 30 hosts the Spreadsheet program, the CustomerDatabase and the Word Processor. User A is authorized to use theSpreadsheet, User B is authorized to use the Customer Database, and nousers are authorized to use the Word Processor. It is to be understoodthat other techniques can be used to indicate who is authorized to use aparticular application. For example, the user information stored in thedatabase can be used to indicate those users who are unauthorized to usea particular application rather than those who are authorized, or toindicate that multiple users may access a resource on a remote machine30, or to indicate that a predetermined group of users are authorized toaccess a particular resource. Although Table 2 depicts an embodiment inwhich the resources that are available are application programs, asimilar technique may be used for computing environments and otherresources.

To obtain the information that is stored in the resource authorizationcache 448, the remote machine 30 obtains the resource-relatedinformation from each other machine in the machine farm 38 regarding theresources on those remote machines, including control information thatindicates which client users and remote machines are permitted to accesseach particular resource. The resource-related information maintained inthe database may or may not persist across re-boots of the remotemachine 30.

Each remote machine 30 having the Resource Neighborhood applicationinstalled thereon executes the RNSVC software 444. The RNSVC software444, operating on each remote machine 30 establishes a communicationlink (e.g. a named pipe) with at least one other and, in someembodiments, each other remote machine 30. The remote machines 30exchange resource-related information on the communications links. Inanother embodiment, the RNSVC software 444 collects the resource-relatedinformation from the other remote machine 30 in the machine farm 38through remote registry calls (e.g., the service component 444 transmitsa datagram to other remote machine 30 in the farm 38 requesting theresource-related information corresponding to the resources hosted bythose remote machine 30). In some embodiments the resource authorizationcache is populated by system administrators of by programs and scriptscommunicating with remotes machines 30. The RNSVC 444 software alsomaintains the relationships of groups and users to published resourcesin the resource authorization cache 448 and accesses the informationwhen authenticating a client user. An administrator of the remotemachine 30 can use a user interface to configure the RNSVC 444.

Other functions of the RNSVC software 444 include implementing theservices and functions requested by the RNAPI 452 and communicating withthe RNAPI 452 on the client machine 10 using a Resource Neighborhoodvirtual channel driver (VCRN). The VCRN operates according to theResource Neighborhood virtual channel protocol described.

The RNAPI 452 is a set of software functions or services that are usedby the Resource Neighborhood application to perform various operations(e.g., open windows on a display screen, open files, and display messageboxes). The RNAPI 452 provides a generic mechanism for accessing userinterface elements (e.g., icons) produced by running the ResourceNeighborhood application and objects in a legacy (i.e., predecessor orexisting for some time) client user interface. When the client machine10 accesses an available resource, the accessing mechanism can launchthe resource on the remote machine 30, if necessary (e.g., when theclient machine 10 is unable to locally execute the application).

The RNAPI 452 provides all published resource information to the userinterface component 456 for display on the screen 12 (FIG. 1) of theclient machine 10. The RNAPI 452 also manages machine farm 38 logons ina local database of logon credentials (e.g., passwords) for users of theclient machine 10 to support the single authentication feature.Credentials may or may not be persistent across a reboot (power-off andon cycles) of the client machine 10.

The RNAPI 452 provides automatic and manual management for ResourceNeighborhood objects stored in the local cache 460. The local cache 460can either be refreshed manually by the user of the client machine 10,or at a user-definable refresh rate, or by the server at any time duringa connection. In a Windows implementation, the RNAPI 452 can buildremote application file resource associations and manage the “Start”menu and desktop icons for resource object shortcuts.

The user interface module 456 interfaces the RNAPI 452 and can be afunctional superset of an existing client user interface (e.g., RemoteResource Manager). The user interface module 456 accesses theinformation stored in the local cache 460 through the RNAPI 452 andvisually presents that information to the user on the display screen 12(FIG. 1) of the client machine 10. The displayed information is amixture of information generated by a user of the client machine 10 andinformation obtained by the Resource Neighborhood application. The userinterface module 456 can also show the user all resources that the useris currently accessing and all active and disconnected sessions.

In a Windows-based embodiment, the user interface module 456 can presenta variety of graphical components, such as windows and pull-down menus,to be displayed on the display screen 12 (FIG. 1). A display of acombination of such graphical user interface components is generallyreferred to as a “desktop.” A desktop produced by the user interfacemodule 456 can include a Resource Neighborhood window displaying theneighborhood of resources available to the user of the client machine10. These resources may be a filtered combination of the publishedresources hosted by a machine farm 38. The user interface module 456 cangenerate a Resource Neighborhood window for each machine farm 38 ormerge the resources from different machine farms 38 under a singleResource Neighborhood window.

At a top level, the Resource Neighborhood window includes a folder foreach machine farm 38. Clicking on one of the folders produces a windowcontaining a representation (e.g., an icon) of each hosted resourceavailable to the user, e.g., see FIGS. 6A and 6B. The ResourceNeighborhood window becomes the focal point for accessing publishedresources, and the user interface module 456 can be used to accessresources and launch applications through the RNAPI 452. For example,the user of the client machine 10 can use the mouse 18 (FIG. 1) toselect one of the displayed icons and launch the associated resource.

A feature of a client-based implementation is that the user can browsethe objects displayed in the Resource Neighborhood window although theclient machine is offline, that is, the connection 462 is inactive.Also, a user of the client machine 10 can drag application objects andfolders out of the Resource Neighborhood window and into other graphicalcomponents (e.g., other windows, folders, etc.) of the desktop.

FIG. 5 shows one embodiment of the program components for a server-basedimplementation of the Resource Neighborhood application. The componentsinclude a Service (RNSVC) component 544′, a Resource Database component548′, an Application Program Interface (RNAPI) component 552′, a UserInterface component 556′ and a local cache 560′. Each software component544′, 548′, 552′, 556′, and 560′ is installed on the application server30′. The software components for the server-based implementationcorrespond to the software components for the client-basedimplementation of FIG. 4. The functionality of each server-basedsoftware component is similar to the client-based counterpart, withdifferences or added capabilities described below. The RNSVC 544′communicates with the resource database 548′ and with the RNAPI 552′using local procedure calls. The RNAPI 552′ also communicates with theuser interface module 556′ and the local cache 560′.

Similar to that described in FIG. 4 for the client machine 10, theclient machine 10 logs on to the network 40 (FIG. 1), the server 30′develops and maintains a database containing the resource relatedinformation collected from the other machines in the machine farm 38,and a communication link is established between the server 30′ and theclient machine 20. The application server 30′ may be in communicationwith the client machine 10 via an ICA connection 562′.

To run the Resource Neighborhood application in a server-basedimplementation, the user of the client machine 10 connects to an initialdesktop (at the server 30′) and launches the Resource Neighborhoodapplication from within that desktop environment. The connection to theinitial desktop can occur automatically, e.g., via a logon script of theclient machine 20, via an entry in a Startup group, or by anothercentrally managed server specific mechanism. All remote applicationmanagement and launching is accomplished through this initial desktop.

Similar to that described in FIG. 4 for the server 30, the server 30′uses the user credentials to determine those resources that the user ofthe client machine 10 is authorized to use. A Resource Neighborhoodgraphical window is returned to the client machine 10 and displayed onthe client screen 22 (FIG. 1). This window can contain iconsrepresenting the available and, possibly, the unavailable resources thatare in the Resource Neighborhood of the client machine 20.

In one embodiment, the web-based Resource Neighborhood applicationincludes a group of objects that manage various aspects of a resource.In one embodiment, the Resource Neighborhood application includes threeprimary object classes that “plug in” to a web server: a gateway objectclass; a credentials object class; and a resources object class. In somespecific embodiments, the object classes are provided as JavaBeans. Thethree primary object classes facilitate: validation of user credentialsinto a server farm; generation of lists of published resources that aspecified user may access; provisioning of detailed information about aspecific published resource; and conversion of resource applicationinformation into a format compatible with the protocol over whichconnection will be made.

When provided as JavaBeans, the objects can be accessed in a number ofdifferent ways. For example, they may be compiled as COM objects andmade available to the web server as ActiveX components. In anotherembodiment, the JavaBeans can be used in their native form, such as whenthe server uses Java Server Pages technology. In yet another embodiment,the JavaBeans can be instantiated and used directly in a Java Servlet.In still another embodiment, the remote machine 30 can instantiate theJavaBeans as COM objects directly.

A credentials object class manages information necessary to authenticatea user into a target machine farm 38. A credentials object passes storeduser credentials to other Resource Neighborhood objects. In someembodiments, the credentials object is an abstract class that cannot beinstantiated and represents a user's credentials. Various classextensions may be provided to allow different authentication mechanismsto be used, including biometrics, smart cards, token-basedauthentication mechanisms such as challenge-response and time-basedpassword generation, or others. For example, a “clear text credentials”extension may be provided that stores a user's name, domain, andpassword in plain text.

A gateway object class handles communications with a target machine farm38. In one embodiment, the gateway object class is provided as anabstract Java class that cannot be instantiated. A particular gatewayobject may retrieve resource information by communicating with a machinefarm 38 using a particular protocol, reading cached resourceinformation, a combination of these two methods, or other variousmethods.

As noted above, the gateway object class may cache information tominimize communication with a target machine farm 38. Extensions to thegateway object may be provided to communicate with the machine farm 38over specific protocols, such as HTTP. In one embodiment, an extensionclass is provided that allows the gateway object to communicate with themachine farm 38 via WINDOWS NT named pipes. The gateway object mayprovide an application programming interface hook that allows otherResource Neighborhood objects to query the object for applicationinformation.

A resources object class contains information about published resourcesand returns information about resources hosted by the machine farm 38 inorder to create the Resource Neighborhood web page. The resources objectclass creates objects representing resources by retrieving informationrelating to the resources, either from an object created by the gatewayobject or directly from the machines in the machine farm 38. A resourcesobject acts as a container for certain properties of the resource, somesettable and some not settable, such as: the name of the resource (notsettable); the width of the client window, in pixels, for this resource(settable); the height of the client window, in pixels, for thisresource (settable); the number of colors to use when connecting to theresource (settable); the severity of audio bandwidth restriction(settable); the level of encryption to use when connecting to theresource (settable); the level of video to use when connecting to thisresource (settable); whether the resource should be placed on a client'sstart menu (settable); whether the resource should be placed on theclient's desktop (settable); the identity of the Resource Neighborhoodfolder to which the resource belongs (settable); the description of theresource (settable); the source of the graphics icon file for theresource (settable); the type of window that should be used whenconnecting to the resource (not settable); and whether to overridedefault parameters for the object.

FIG. 6A is a screenshot of one embodiment of Resource Neighborhoodwindow 620 that can be displayed on the screen 12, 22 (FIG. 1) of aclient machine 10,10′ after the Resource Neighborhood application hasexecuted. The window 120 includes graphical icons 622. Each icon 622represents a resource that is hosted by one of the machines in a machinefarm 38. Each represented resource is available to the user of theclient machine 10. The user can select one of the resources using themouse 18, 28 or keyboard 14, 24.

FIG. 6B is a screenshot of another embodiment of a Resource Neighborhoodwindow 624 that can be displayed on the screen 12, 22 (FIG. 1) of aclient machine 10, 10′ after the Resource Neighborhood application hasexecuted. The window 624 includes graphical icons 626, 628. Each icon626, 628 represents a resource that is hosted by one of the machines ina machine farm 38. Each resource represented by one of the icons 626 isavailable to the user of the client machine 10. The user can select oneof the resources using the mouse 18, 28 or keyboard 14, 24. Forweb-based Resource Neighborhood environments, the screenshots of FIGS.6A and 6B are similar, except that icons 622, 626, 628 are displayedwithin a browser window.

Each resource represented by one of the icons 628 is unavailable to theuser of the client machine 10, although such resources are present inthe server farm. The unavailability of these resources can be noted onthe display screen (e.g., “X”s can be drawn through the icons 628). Anattempt to access such a resource can trigger a message indicating thatthe user is not authorized to access the resource. Alternatively, theattempt may invoke a method allowing the user of the client machine 10to request access to the resource.

In some embodiments, the resource comprises a computing environment. Inone of these embodiments, a connection is established between the clientmachine 10 and a virtual machine hosting the requested computingenvironment. In one embodiment, a presentation layer protocol is used inestablishing the connection between the client system and the virtualmachine. In another embodiment, the X11 protocol is used in establishingthe connection. In still another embodiment, the Remote Desktop Protocol(RDP) is used in establishing the connection. In yet another embodiment,the Independent Computing Architecture (ICA) protocol is used inestablishing the connection.

In some embodiments, a connection is established between the clientmachine 10 and a physical machine, such as a traditional workstation orserver, hosting the requested computing environment. In otherembodiments, a connection is established between the client machine 10and a hardware partition hosting the requested computing environment.

In some embodiments, an enumeration of a plurality of resourcesavailable to the client machine 10 is provided (step 204) responsive toa determination by a policy engine regarding whether and how a clientmachine may access a resource. The policy engine may collect informationabout the client machine prior to making the determination. Referringnow to FIG. 7A, one embodiment of a computer network is depicted whichincludes a client machine 10, a machine farm 38, a collection agent 704,a policy engine 706, a policy database 708, and a resource server 30′.In one embodiment, the policy engine 706 is a remote machine 30.Although only one client machine 10, collection agent 704, policy engine706, machine farm 38, and resource server 30′ are depicted in theembodiment shown in FIG. 7A, it should be understood that the system mayprovide multiple ones of any or each of those components.

In brief overview, when the client machine 10 transmits the policyengine 706 a request 206 for a resource enumeration, the collectionagent 704 communicates with the client machine 10, retrievinginformation about the client machine 10, and transmits the clientmachine information 712 to the policy engine 706. The policy engine 706makes an access control decision by applying a policy from the policydatabase 708 to the received information 712.

In more detail, the client machine 710 transmits to the policy engine706 a request 206 for resource enumeration. In one embodiment, thepolicy engine 706 resides on a resource server 30′. In anotherembodiment, the policy engine 706 resides on a remote machine 30. Instill another embodiment, a resource server 30′ receives the request 206from the client machine 10 and transmits the request 206 to the policyengine 706. In yet another embodiment, the client machine 10 transmits arequest 206 for resource enumeration to an intermediate remote machine30′″ (not shown), which transmits the request 206 to the policy engine706.

In some embodiments, the client machine 10 transmits the request 206over a network connection such as those described above. Upon receivingthe request, the policy engine 706 initiates information gathering bythe collection agent 704. The collection agent 704 gathers informationregarding the client machine 10 and transmits the information 712 to thepolicy engine 706.

In some embodiments, the collection agent 704 gathers and transmits theinformation 712 over a network connection. In some embodiments, thecollection agent 704 comprises bytecode, such as an application writtenin the bytecode programming language JAVA. In some embodiments, thecollection agent 704 comprises at least one script. In thoseembodiments, the collection agent 704 gathers information by running atleast one script on the client machine 10. In some embodiments, thecollection agent comprises an Active X control on the client machine 10.An Active X control is a specialized Component Object Model (COM) objectthat implements a set of interfaces that enable it to look and act likea control.

In one embodiment, the policy engine 706 transmits the collection agent704 to the client machine 10. In some embodiments, the policy engine 706requires another execution of the collection agent 704 after thecollection agent 704 has transmitted information 712 to the policyengine 706. In some of these embodiments, the policy engine 706 requiresanother execution of the collection agent 704 because the policy engine706 may have insufficient information 712 to determine whether theclient machine 10 satisfies a particular condition. In otherembodiments, the policy engine 706 requires a plurality of executions ofthe collection agent 704 in response to received information 712.

In some embodiments, the policy engine 706 transmits instructions to thecollection agent 704 determining the type of information the collectionagent 704 gathers from the client machine 10. In those embodiments, asystem administrator may configure the instructions transmitted to thecollection agent 704 from the policy engine 706. This provides greatercontrol over the type of information collected. This also expands thetypes of access control decisions that the policy engine 706 can make,due to the greater control over the type of information collected. Thecollection agent 704 gathers information 712 including, withoutlimitation, machine ID of the client machine 10, operating system type,existence of a patch to an operating system, MAC addresses of installednetwork cards, a digital watermark on the client device, membership inan Active Directory, existence of a virus scanner, existence of apersonal firewall, an HTTP header, browser type, device type, networkconnection information such as internet protocol address or range ofaddresses, machine ID of the remote machine 30, date or time of accessrequest including adjustments for varying time zones, and authorizationcredentials.

In some embodiments, the device type is a personal digital assistant. Inother embodiments, the device type is a cellular telephone. In otherembodiments, the device type is a laptop computer. In other embodiments,the device type is a desktop computer. In other embodiments, the devicetype is an Internet kiosk. In still other embodiments, the device typeis a game console.

In some embodiments, the digital watermark includes data embedding. Insome embodiments, the watermark comprises a pattern of data insertedinto a file to provide source information about the file. In otherembodiments, the watermark comprises hashed data files to provide tamperdetection. In other embodiments, the watermark provides copyrightinformation about the file.

In some embodiments, the network connection information pertains tobandwidth capabilities. In other embodiments, the network connectioninformation pertains to the Internet Protocol address of the clientmachine 10. In still other embodiments, the network connectioninformation consists of the Internet Protocol address of the clientmachine 10. In one embodiment, the network connection informationcomprises a network zone identifying the logon agent to which the clientmachine 10 provided authentication credentials.

In some embodiments, the authorization credentials include a number oftypes of authentication information, including without limitation, usernames, client names, client addresses, passwords, PersonalIdentification Numbers (PINs), voice samples, one-time passcodes,biometric data, digital certificates, tickets, etc. and combinationsthereof. After receiving the gathered information 712, the policy engine706 makes an access control decision based on the received information712.

Referring now to FIG. 7B, a block diagram depicts one embodiment of apolicy engine 706, including a first component 720, including acondition database 722 and a logon agent 724, and a second component730, including a policy database 732. The first component 720 applies acondition from the condition database 722 to information 712 receivedabout client machine 10 and determines whether the received information712 satisfies the condition.

In some embodiments, a condition may require that the client machine 10execute a particular operating system to satisfy the condition. In otherembodiments, a condition may require that the client machine 10 executea particular operating system patch to satisfy the condition. In stillother embodiments, a condition may require that the client machine 10provide a MAC address for each installed network card to satisfy thecondition. In some embodiments, a condition may require that the clientmachine 10 indicate membership in a particular Active Directory tosatisfy the condition. In another embodiment, a condition may requirethat the client machine 10 execute a virus scanner to satisfy thecondition. In other embodiments, a condition may require that the clientmachine 10 execute a personal firewall to satisfy the condition. In someembodiments, a condition may require that the client machine 10 comprisea particular device type to satisfy the condition. In other embodiments,a condition may require that the client machine 10 establish aparticular type of network connection to satisfy the condition.

If the received information satisfies a condition, the first component720 stores an identifier for that condition in a data set 726. In oneembodiment, the received information satisfies a condition if theinformation makes the condition true. For example, a condition mayrequire that a particular operating system be installed. If the clientmachine 10 has that operating system, the condition is true andsatisfied. In another embodiment, the received information satisfies acondition if the information makes the condition false. For example, acondition may address whether spyware exists on the client machine 10.If the client machine 10 does not contain spyware, the condition isfalse and satisfied.

In some embodiments, the logon agent 724 resides outside of the policyengine 706. In other embodiments, the logon agent 724 resides on thepolicy engine 706. In one embodiment, the first component 720 includes alogon agent 724, which initiates the information gathering about clientmachine 10. In some embodiments, the logon agent 724 further comprises adata store. In these embodiments, the data store includes the conditionsfor which the collection agent may gather information. This data storeis distinct from the condition database 722.

In some embodiments, the logon agent 724 initiates information gatheringby executing the collection agent 704. In other embodiments, the logonagent 724 initiates information gathering by transmitting the collectionagent 704 to the client machine 10 for execution on the client machine10. In still other embodiments, the logon agent 724 initiates additionalinformation gathering after receiving information 712. In oneembodiment, the logon agent 724 also receives the information 712. Inthis embodiment, the logon agent 724 generates the data set 726 basedupon the received information 712. In some embodiments, the logon agent724 generates the data set 726 by applying a condition from the database722 to the information received from the collection agent 704.

In another embodiment, the first component 720 includes a plurality oflogon agents 724. In this embodiment, at least one of the plurality oflogon agents 724 resides on each network domain from which a clientmachine 10 may transmit a resource request 710. In this embodiment, theclient machine 10 transmits the resource request 710 to a particularlogon agent 724. In some embodiments, the logon agent 724 transmits tothe policy engine 706 the network domain from which the client machine10 accessed the logon agent 724. In one embodiment, the network domainfrom which the client machine 10 accesses a logon agent 724 is referredto as the network zone of the client machine 10.

The condition database 722 stores the conditions that the firstcomponent 720 applies to received information. The policy database 732stores the policies that the second component 730 applies to thereceived data set 726. In some embodiments, the condition database 722and the policy database 732 store data in an ODBC-compliant database.For example, the condition database 722 and the policy database 732 maybe provided as an ORACLE database, manufactured by Oracle Corporation ofRedwood Shores, Calif. In other embodiments, the condition database 722and the policy database 732 can be a Microsoft ACCESS database or aMicrosoft SQL Server database, manufactured by Microsoft Corporation ofRedmond, Wash.

After the first component 720 applies the received information to eachcondition in the condition database 722, the first component transmitsthe data set 726 to second component 730. In one embodiment, the firstcomponent 720 transmits only the data set 726 to the second component730. Therefore, in this embodiment, the second component 730 does notreceive information 712, only identifiers for satisfied conditions. Thesecond component 730 receives the data set 726 and makes an accesscontrol decision by applying a policy from the policy database 732 basedupon the conditions identified within data set 726.

In one embodiment, policy database 732 stores the policies applied tothe received information 712. In one embodiment, the policies stored inthe policy database 732 are specified at least in part by the systemadministrator. In another embodiment, a user specifies at least some ofthe policies stored in the policy database 732. The user-specifiedpolicy or policies are stored as preferences. The policy database 732can be stored in volatile or non-volatile memory or, for example,distributed through multiple servers.

Using the policy engine 706 as just described, an access controldecision based upon information received about a client machine 10 ismade. Upon receiving gathered information about the client machine 10,the policy engine 706 generates a data set based upon the information.The data set contains identifiers for each condition satisfied by thereceived information 712. The policy engine 706 applies a policy to eachidentified condition within the data set 726. That application yields anenumeration of resources which the client machine 10 may access. In someembodiments, the enumeration of resources includes an enumeration oflevels of access to the resource. In one of these embodiments, aplurality of allowable actions associated with the resource isenumerated. In another of these embodiments, a plurality of methods ofexecution of the resource is enumerated. The policy engine 706 thenpresents that enumeration to the client machine 10. In some embodiments,as described above in connection with FIGS. 6A and 6B, the policy engine706 creates a Hypertext Markup Language (HTML) document used to presentthe enumeration to the client machine.

In some embodiments, the policy engine 706 transmits the enumeration toa different remote machine 30. In one of these embodiments, the remotemachine 30 transmits the enumeration to the client machine 10. Inanother of these embodiments, the remote machine 30 applies additionalpolicies to the enumeration. In still another of these embodiments, theremote machine is an appliance such as an application gateway or afirewall. In some of these embodiments, the policy engine 706 transmitsan assigned level of action applicable to a requested resource to aremote machine 30 functioning as a broker server. The broker serverestablishes, responsive to the assigned level of access, a connectionbetween the client machine 10 and a computing environment providing therequested resource.

Referring now to FIG. 8, a flow diagram depicts one embodiment of thesteps taken to provide access to a resource. In brief overview, arequest for access to a resource is received (step 802). A method forproviding access to the resource is identified (step 804). Anapplication execution server may be selected to provide access to theresource (step 806). A virtualized environment may be selected toprovide access to a resource (step 808). An application streamingservice may be selected to provide access to the resource (step 816). Ifthe virtualized environment is selected to provide access to theresource, an execution machine is identified (step 810). A virtualmachine is selected (step 812). The virtual machine is configured (step814). Access to the resource is provided (step 818).

Still referring to FIG. 8, and in more detail, a request for access to aresource is received (step 802). In one embodiment, a remote machine 30receives the request. In some embodiments, the remote machine 30 is anintermediate broker server. In other embodiments, the remote machine 30is a gateway. In still other embodiments, the remote machine 30 is apolicy engine. In yet other embodiments, the remote machine 30 is anappliance.

In one embodiment, the remote machine 30 verifies that the user isauthorized to access the resource. In still another embodiment, theremote machine 30 receives with the request information verifyingauthorization for access by the user.

In one embodiment, the remote machine 30 receives a request for anapplication program. In another embodiment, the remote machine 30receives a request for access to a file. In yet other embodiments, theremote machine 30 receives a request for access to a computingenvironment. In one of these embodiments, the computing environment is adesktop environment from which the client machine 10 may executeapplication programs. In another of these embodiments, the computingenvironment provides access to one or more application programs. In someembodiments, the remote machine 30 receives a request for access to acomputing environment supported by a plurality of hardware requirements.In some embodiments, a remote machine 30 functioning as deploymentsystem receives a request for access to a resource, such as execution ofan application program, from a client machine 10.

A method for providing access to the resource is identified (step 804).In one embodiment, a remote machine 30 consults a database to identifythe method for providing access. In another embodiment, a remote machine30 consults a policy or rules database to identify the method forproviding access. In still another embodiment, a remote machine 30receives from a policy engine an identification of a method to select.

For embodiments in which the resource is an application program, apolicy may allow execution of the application program on the clientmachine 10. In another of these embodiments, a policy may enable theclient machine 10 to receive a stream of files comprising theapplication program. In this embodiment, the stream of files may bestored and executed in an isolation environment on the client. In stillanother of these embodiments, a policy may allow execution of theapplication program only on a remote machine, such as an applicationserver, and require the remote machine to transmit application-outputdata to the client machine 10. In yet another of these embodiments, apolicy may allow execution of the application program only in acomputing environment hosted on a virtual machine. In either of thesecases, a stream of files comprising the application programs may be sentto the remote machine.

For embodiments in which the resource is a computing environment, apolicy may allow installation of the computing environment on the clientmachine 10. In another of these embodiments, a policy may enable theclient machine 10 to access a copy of the computing environmentexecuting in a virtual machine on a remote machine 30. In still anotherof these embodiments, a policy may forbid the user of the client machine10 to access the requested computing environment and offer analternative computing environment.

For embodiments in which the resource is a computing environmentsupported by a plurality of hardware resources, a policy may enable theclient machine 10 to access a copy of the computing environmentexecuting in a virtual machine, which in turn executes on a hypervisorproviding access to the requested plurality of hardware resources. Instill another of these embodiments, a policy may forbid the user of theclient machine 10 to access the requested computing environment andoffer a computing environment supported by an alternative plurality ofhardware resources.

The remote machine 30 may choose to provide access to an applicationexecution server which provides access to a requested applicationprogram (step 806). The application execution server executes theapplication program and transmits application output data to the clientmachine 10. The application execution server may transmit theapplication output data over a presentation layer protocol, such as X11,VNC, ICA, or RDP.

Referring back to step 804, the remote machine 30 may choose to provideaccess to an application streaming service capable of transmitting arequested application program to the client machine 10 (step 816) forexecution. Embodiments of application streaming services are describedin greater detail below.

Referring back to step 804, the remote machine 30 may choose to respondto the client's request by allowing access to a computing environmentprovided by a virtual machine, the computing environment providingaccess to the requested resource (step 808). The computing environmentmay be provided by a virtual machine launched into a hypervisorexecuting on a remote machine 30′. In other embodiments, the remotemachine 30 determines to provision on the client machine 10 a virtualmachine providing access to the computing environment.

In embodiments where a remote machine 30 determines to provide access tothe requested resource via a virtualized environment, the remote machine30 identifies an execution machine providing access to a computingenvironment requested by the client machine 10 (step 810). In one ofthese embodiments, the remote machine 30 identifies an execution machinecapable of hosting the computing environment. In another of theseembodiments, the remote machine 30 determines that the user requestingaccess to the computing environment lacks authorization to access therequested computing environment. The remote machine 30 may identify analternative computing environment which the user is authorized toaccess. In still another of these embodiments, the remote machine 30identifies an execution machine on which a hypervisor provides access toa requested plurality of hardware and in which the requested computingenvironment may execute.

In other embodiments, the remote machine 30 is an execution machinecapable of hosting the computing environment. In some of theseembodiments, the computing environment is installed on the executionmachine. In others of these embodiments, a hypervisor on the executionmachine emulates a plurality of hardware resources required by therequested computing environment and the computing environment islaunched in the hypervisor.

In some embodiments, the remote machine 30 identifies a remote machine30′ functioning as an execution machine capable of providing access tothe computing environment supported by a requested plurality of hardwareresources. In one of these embodiments, the remote machine 30′ functionsas an execution machine on which a hypervisor emulating the requestedplurality of hardware resources executes and on which a computingenvironment supported by the hypervisor executes.

In some embodiments, an execution machine providing hardware resources,physical or virtual, capable of supporting a particular virtual machineis identified responsive to a load-balancing determination. In one ofthese embodiments, the execution machine is selected responsive toload-balancing information maintained by a management server 30. In someembodiments, the management server 30 is a single machine. In stillother embodiments, several remote machines 30 may be capable of actingas a management server, but only one of such nodes is designated themanagement server. In some embodiments, a client request is directed tothe management server 30 in the first instance. In other embodiments, aremote machine 30 queries the management server 30 to determine theidentity of a suitable execution machine.

The master network information server node 30 maintains a table ofaddresses for the remote machines 30′, 30″. In addition, the masternetwork information server node 30 receives messages from the remotemachines 30′, 30″ indicating their level of activity, which may compriseCPU load or may comprise an identification of the number of a virtualmachines currently hosted by a remote machine 30′, 30″. The level ofactivity of the remote machines 30′, 30″ is maintained in a table alongwith the address of each of the remote machines 30′, 30″.

For embodiments, in which a single management server 30 is used, it isdesirable to dynamically select a master network information server node30 from the available remote machines 30 on the network. In this way, ifthe active management server 30 fails, a new management server 30 may beselected as soon as the failure of the previous management server 30 isdetected. In one embodiment a management server 30 is selected by anelection process among the remote machines 30.

In one embodiment, any machine (client machine 10 or remote machine 30)may force an election at any time by broadcasting a request electiondatagram to the machine farm 38. The election results are determined bya comparison of the set of election criteria which is transmitted withinthe request election datagram transmitted by the requesting node withthe set of election criteria maintained on each receiving node. That is,the first election criterion from the datagram of the requesting node iscompared by the receiving node to the first criterion of the receivingnode. The highest ranking of the two criteria being compared wins thecomparison and the node with that criterion wins the election. If thetwo criteria tie, then the next criteria are sequentially compared untilthe tie is broken. If a remote machine 30 receiving the request electiondatagram has a higher election criterion than that received in therequest election datagram, the remote machine 30 receiving the requestelection datagram issues its own request election datagram. If thereceiving remote machine 30 has a lower election criteria than thecriteria received in the request election datagram, the receiving remotemachine 30 determines it is not the master network information servernode and attempts to determine which remote machine 30 in the machinefarm 38 is the management server 30.

In one embodiment the criteria which determine the outcome of theelection include: whether or not the node is statically configured as amaster network information server node; whether the remote machine 30has the higher master network information server software versionnumber; whether the remote machine 30 is an NT domain controller;whether the remote machine 30 is the longest running node; and whetherthe remote machine 30 has a lexically lower network name. In oneembodiment, the datagram structure for the election request includes anunsigned shortword for the server version number, an unsigned shortwordin which the bits are flags which designate whether the node isstatically configured as a master network information server node, or isexecuting on a NT domain controller and an unsigned longword containingthe amount of time the server has been running.

Periodically, the management server 30 transmits a declare message tothe other remote machines 30 declaring itself to be the managementserver 30. If another remote machine 30 believes itself to be amanagement server 30, the other remote machine 30 will request anelection. In this way erroneous master network information server nodes30 of the same protocol are detected and removed. In addition anelection will also be requested: by any remote machine 30 when thatremote machine 30 reboots; by any remote machine 30 to whom the masternetwork information server node has failed to acknowledge an updatemessage; or any client machine 10 to whom the master network informationserver node 30 has failed to respond to a request for information.

In more detail and referring to FIG. 9, once any remote machine 30(which may be referred to as a node) broadcasts a request electiondatagram requesting an election (Step 920), the remote machine 30receiving the request election datagram (Step 924) first compares itselection criteria to the criteria in the request election datagram (Step930) to determine if the receiving remote machine 30 has higher criteria(Step 934). If the remote machine 30 receiving the datagram has lowerelection criteria (Step 938) than the criteria contained in the requestelection datagram, the remote machine 30 receiving the request electiondatagram drops out of the election process and awaits the results of theelection (Step 938).

If the remote machine 30 receiving the request election datagram hashigher election criteria than that contained in the request electiondatagram, then the remote machine 30 receiving the request electiondatagram broadcasts its own request election datagram containing theremote machine's own election criteria (Step 940). If in response to thetransmission of the request election datagram by the second remotemachine 30, another remote machine 30′ responds with a request electiondatagram with even higher election criteria, then the second remotemachine 30 drops out of the election and the remote machine 30′ withhigher criteria broadcasts it's own request election datagram. If noother remote machine 30 responds with higher election criteria, the nodewhich has apparently won the election for master network informationserver node sends n more election requests, (in one embodiment threerequests) (Step 956) and then if still no other remote machine 30responds with higher election criteria, the remote machine 30 which hassent the n election requests is the new management server 30.

After the election has occurred and the new management server 30 hasbeen determined, all the remote machines 30 send all of their configuredgateway addresses to the new network information server node 30. In thisway the new management server 30 becomes a gateway node.

Referring again to FIG. 1, once the management server 30 is elected, theremote machines 30 send update datagrams to the master networkinformation server 30 providing information about each remote machine 30transmitting the update datagram. In one embodiment, the update datagramsent to the master network information server node 30 from a remotemachine 30 includes: the remote machine 30 name; the network address;the cluster name; the network transport protocol; the total number ofremote machines 30 configured with this transport; the number of portsavailable for connection with a client using this transport protocol;the total number of users permitted to be active at one time; number ofavailable user slots; and server load level. Upon receipt of the updatedatagram, the master network information server node 30 returns anacknowledgment to the remote machines 30 that transmitted the updatedatagram indicating that the update datagram was received. If the remotemachine 30 transmitting the update datagram does not receive anacknowledgment from the master network information server node 30, thetransmitting remote machine 30 assumes that the master networkinformation server node 30 has failed and transmits an election request.

In more detail and referring to FIG. 10, a remote machine 30, after theelection of a management server 30, waits a random period of time andthen sends a datagram to the management server 30 with its latest loadinformation (Step 1000). In one embodiment the delay is between four andsix seconds. If the management server 30 receives (Step 1008) an updatedatagram from a remote machine 30, then the master network informationserver node 30 replies to the transmitting remote machine 30 with anacknowledgment (Step 1010) and forwards the data to any remote machine30 configured as a gateway node. If the master network informationserver 30 fails to receive data from a remote machine 30 (Step 1008),then the master network information server 30 discards the old data fromthe remote machine 30 after a predetermined amount of time (Step 1020).

If the remote machine 30 does not receive an acknowledgment from themaster network information server node 30 after the remote machine 30has sent an update datagram (Step 1028), the remote machine 30retransmits the update datagram. The remote machine 30 will attempt nretransmits (in one embodiment three) before it assumes that the masternetwork information server 30 has failed and then transmits an electionrequest (Step 1030). If the remote machine 30 receives anacknowledgment, then it periodically updates the master networkinformation server node 30, in one embodiment every 5 to 60 minutes(Step 1040).

In some embodiments, a remote machine's participation in the activitiesjust described is controlled by a virtual machine executing in thehypervisor rather than by an operating system. FIG. 11 is a blockdiagram depicting one embodiment of a machine farm 38 including a firstand second network management processes. The first network managementprocess 1110 executes in a native operating system 1105 (such as WINDOWSNT) and accesses a native memory element storing (i) a data table and(ii) at least one election criteria for allowing the first networkmanagement process 1110 to be dynamically selected as a managementprocess, the data table having an entry for each of said at least twonetwork management processes. The second network management process 1120executes in a virtualized operating system 1115 and accesses avirtualized memory element storing (i) a data table and (ii) at leastone election criteria for allowing the second network management process1120 to be dynamically selected as the management process, the datatable having an entry for each of said at least two network managementprocesses. The client machine 10 communicates with the one of the firstnetwork management process 1110 and the second network managementprocess 1120 selected as the management process and receives from themanagement process an address of a remote machine 30 with which tocommunicate. In some embodiments, a plurality of client machines 10 isin communication with a master network information process.

The first network management process 1110 executes in a native operatingsystem 1105. The second network management process 1120 executes in avirtualized operating system 1115. In one embodiment, the at least twonetwork management processes are grouped into clusters. In anotherembodiment, one of the at least two network processes is a gatewayprocess. In still another embodiment, the gateway process is a masternetwork management process. In some embodiments, the master networkmanagement process is selected by a process comprising the steps of (a)broadcasting an election datagram to the at least two network managementprocesses, the election datagram comprising election criteria; and (b)selecting a master network management process in response to theelection criteria. In one of these embodiments, the master networkmanagement process broadcasts a declare datagram to detect multiplemaster network management processes using the same transport protocol.In another of these embodiments, the master network management processis selected by a process that occurs after an event selected from thegroup of events consisting of: a system reboot, a master networkmanagement process failing to respond to a datagram sent from a networkmanagement process, a master network management process failing torespond to a request from a client machine, detection of at least twomaster network management processes configured with the same transport,and a new network management process appearing on said network.

In one embodiment, the management process is elected as described abovein connection with FIGS. 9 and 10.

In some embodiments, the network includes a third network managementprocess using a different network transport protocol from the firstnetwork management process. In one of these embodiments, the thirdnetwork management process comprises a master network management processfor the different network transport protocol.

For embodiments in which machine farm management is decentralized, eachremote machine 30 may include a load management subsystem (LMS)providing a load management capability. In general, the LMS managesoverall server and network load to minimize response time to clientrequests.

In some embodiments, an apparatus for selecting a server from a networkplurality of servers to service a client request comprises a pluralityof network management processes. In one of these embodiments, each ofsaid plurality of network management processes includes an event bus anda subsystem in communication with the event bus. In another of theseembodiments, a first one of the plurality of network managementprocesses receives from a client machine a request for access to acomputing resource and sends the client request to a second one of theplurality of network management processes. In still another of theseembodiments, the second one of the plurality of network managementprocesses executes in a virtualized operating system and comprises adynamic store and a load management subsystem.

The dynamic store loads information associated with at least some of theplurality of network management processes in a virtualized memoryelement. In some embodiments, the dynamic store contains informationrelating to server processor load. In other embodiments, the dynamicstore contains information relating to server input/output transactionload.

The load management subsystem (i) receives, via said event bus, arequest to identify a server for servicing a client request, (ii)retrieves from said dynamic store the loading information, (iii)chooses, based on the retrieved loading information, one of theplurality of servers for servicing the client request, and (iv)transmits, via said event bus, a message including informationidentifying the chosen server. In some embodiments, the load managementsubsystem stores run-time information in the dynamic store atpredetermined intervals. In other embodiments, the apparatus furtherincludes a persistent store, the load management subsystem incommunication with the persistent store via the event bus, thepersistent store containing an identification of at least one rule to beused to manage server load.

In one embodiment, the LMS is rule-based, and an administration tool canbe used to modify or create rules for managing server load. A rule isone or more criteria that influences how a LMS will direct requests.Rules may be individualized to a specific remote machine 30. Rules canalso be individualized to a specific application or computingenvironment on a per-server basis. That is, one or more rules may beassociated with a copy of an application or a computing environmentresiding on a first remote machine 30 in the machine farm 38 anddifferent rules may be associated with a copy of the same application orcomputing environment residing on a second remote machine 30 in amachine farm 38. The output of rules individualized to a specificapplication may be combined with the output of general server rules todirect a client request.

Rules use the output from one or more operational meters. Operationalmeters may measure any aspect of server performance and the result isused by rules to help determine which remote machine 30 is mostappropriate to service a client request. For example, operational metersmay measure: processor load; context switches; memory usage; pagefaults; page swaps; transmission rate of input/output reads or writes;number of input/output operations performed or number of virtualmachines hosted. In one embodiment, operational meters are used by a LMSto measure server performance during the occurrence of certain eventssuch as a request for a client connection. In another embodiment,operational meters are used by a LMS to measure server performance atpredetermined intervals, which may be configured by an administrator. ALMS on each remote machine 30 in the machine farm 38 evaluates variousperformance metrics for the remote machine 30 for each predeterminedperiod of time and stores that information in the dynamic store. Forexample, every thirty seconds, an evaluation of server load may includea query to operational meters for server's CPU utilization and memoryutilization. The results from the query will be used, in conjunctionwith other applicable load factors, to calculate a load number for thisserver load. The new load number is then sent to the dynamic store.

Rules and operational meters are, in one embodiment, executable codemodules that query specific system conditions, resources, andperformance metrics for remote machines 30in the machine farm 38. Someof the rules accept user-configurable parameters that are entered by theadministrator via the administration tool. Rules may be provided to theLMS using a dynamic link library (“DLL”), and the rules and ruleparameters applicable to a specific server may be stored in thepersistent store. That is, the administrator's selection of rules isstored, together with a weighting factor and applicable settingsassociated with those rules, in the persistent store. For example, someoperational meters may measure load at a predetermined interval; thepredetermined interval may be set by the administrator.

Examples of conditional rules that may be used by the LMS to determineto which remote machine 30 to direct a request include: whether thenumber of client machines 10 that may connect to a remote machine 30 islimited; whether the number of client sessions that may be serviced by aremote machine 30 is limited; whether the number of virtual machinesthat may be hosted by a remote machine 30 is limited; the number ofapplication or connection licenses available to a remote machine 30;whether the application requested by the client machine 10 is currentlyexecuting on the remote machine 30; whether a client is physicallyproximate to, or is connected by a high bandwidth link to, a server; andwhether a client request is being made during a time period for whichthe remote machine 30 is available to service client requests.

A set of rules may be grouped together by the group subsystem 300 toform a load evaluator associated with a particular server or aparticular application. A server load evaluator is a load evaluator thatapplies to all applications published on the server. An application loadevaluator is a load evaluator that encapsulates rules specific tocertain applications. In one embodiment, loads for published applicationprograms are the sum of a server load evaluator and an application loadevaluator. The load evaluator associated with a particular server may bestored in the persistent store 230. When a LMS initializes, it queriespersistent store 230 to determine whether a load evaluator is associatedwith the remote machine 30 on which the LMS resides. If so, the rulesand operational meters are loaded and the LMS begins using thoseelements of the load evaluator. The outputs of the constituent parts ofthe load evaluator are combined to calculate composite indicia of theload on particular servers, and each LMS stores the results of its loadevaluator in dynamic store. Each rule encapsulated in a load evaluatormay have a configurable weighting factor. Many rules haveuser-configurable parameters that control the way LMS loads arecalculated. For example, in one embodiment, a CPU Utilization rule hastwo parameters: Report Full Load when processor utilization is greaterthan X-percent; report no load when processor utilization is less than Xpercent. In one particular embodiment, the load reported by a loadevaluator equals the sum of each rule's load times each rule's weight.

In another example, a remote machine 30 that hosts four applications mayhave three load evaluators with which it is associated. The serveritself and a first application may by associated with a first loadevaluator, the second and third applications may be associated with asecond load evaluator, and the fourth application may be associated witha third load evaluator. When the remote machine 30 boots, it read thefirst, second, and third load evaluators from the persistent store 230.Periodically (or perhaps after certain events) the remote machine 30calculates the output for each of the load evaluators and sends thosevalues to the dynamic store. When a connection request is received,those values are used to determine if the remote machine 30 shouldservice a client request.

For example, using operational meters the LMS can obtain informationabout the processor load on a particular remote machine 30, the memoryload on that remote machine 30, and the network load of that remotemachine 30. The LMS combines these results to obtain an overall loadnumber that indicates the total aggregate load on that remote machine30. In determining the aggregate load, the load evaluator may weighteach piece of information differently. For embodiments in which a ruleis associated with a remote machine 30, the rule may disqualify a remotemachine 30 from servicing a client request. For example, a rule maylimit the number of client sessions a remote machine 30 may initiate. Inthis embodiment, if a remote machine 30 is currently servicing themaximum number of client sessions allowed by the rule, it will not bechosen by the LMS to service a new client request, even if the outputsof its operational meters indicate that it is the most favorable remotemachine 30 to which to route the client request.

Referring back to FIG. 8, after an execution machine has been selected,a virtual machine providing a requested computing environment isidentified (step 812). In some embodiments, declarative policies such asrules databases, policy databases or scripts are consulted to directrequests to a virtual machine. In other embodiments, a remote machine 30functioning as an application server hosting a plurality of virtualmachines is identified. In one of these embodiments, one of theplurality of virtual machines hosted by the application server may beselected and associated with the client machine 10. In another of theseembodiments, an identifier for the selected virtual machine may betransmitted to the client machine 10.

In some embodiments, a session management component identifies thevirtual machine. In one of these embodiments, an intermediate machine 30receiving the request invokes a session management component. In anotherof these embodiments, the intermediate machine launches the sessionmanagement component in a terminal services session executing on theintermediate machine. In still another of these embodiments, theintermediate machine launches the session management component in aterminal services session executing on the identified execution machine.

In one embodiment, the session management component providesfunctionality for identifying a location of a virtual machine providingaccess to a computing environment. In still another embodiment, thesession management component is provided as a program module publishedon a server, such as an application server. In yet another embodiment,the session management component identifies, launches, and monitorsvirtual machines.

In some embodiments, the session management component communicates witha virtual machine management component to identify a virtual machine. Inone of these embodiments, the virtual machine management componentprovides functionality for locating virtual machines. In another ofthese embodiments, the virtual machine management component providesfunctionality for allocating an available virtual machine to a user froma plurality of available virtual machines. In still another embodiment,the virtual machine management component provides functionality forreallocating shared virtual machines to the plurality of availablevirtual machines. In yet another embodiment, the virtual machinemanagement component provides functionality for tracking a stateassociated with a virtual machine for each virtual machine in aplurality of virtual machines.

Referring now to FIG. 12, a block diagram depicts one embodiment of avirtual machine management component 1200. In one embodiment, thevirtual machine management component 1200 provides functionality foraccessing and updating a database including a virtual machine catalog.In another embodiment, the virtual machine management component 1200provides functionality for allowing an administrator or virtual machineprovisioning system to add, remove, or modify entries in the databaseincluding a virtual machine catalog. In some embodiments, the virtualmachine management component 1200 includes a virtual machine providingadministrative functionality. In other embodiments, the virtual machinecomponent 1200 includes a virtual machine providing managementfunctionality.

In some embodiments, the virtual machine management component 1200 mayreceive a request from a provisioning system or from a sessionmanagement component. In one of these embodiments, a provisioning systemcontacts the virtual machine management component 1200 when a virtualmachine is created or destroyed. In another of these embodiments, thesession management component contacts the virtual machine managementcomponent 1200 when the session management component is invoked torequest a virtual machine to launch. In still another of theseembodiments, the session management component contacts the virtualmachine management component 1200 when the session management componentidentifies a change in a state of a launched virtual machine. Thesession management component may send messages, such as heartbeatmessages, to the virtual machine management component 1200 while avirtual machine is active. If the virtual machine may be accessed bymore than one user, the virtual machine management component 1200 mayreassign the virtual machine to the plurality of available virtualmachines after a user has terminated a session with the virtual machine.

In some embodiments, virtual machines of the same machine type may becategorized into a plurality of standard operating environments (SOE).In one of these embodiments, an SOE may be a group of virtual machineimages of a particular configuration that implement the function of aparticular Machine Type, e.g. a machine type “C++ Developer Workstation”may have one SOE containing images with WinXP Pro SP2 with Visual Studio2003 installed and another SOE containing images with Win Vista withVisual Studio 2005 installed.

In other embodiments, the virtual machine management component 1200 mayprovide functionality for one or more of the following actions relatedto a standard operating environment (an SOE): creating an SOE, updatingan SOE, deleting an SOE, finding an SOE, and retrieving an SOE. In stillanother embodiment, the virtual machine management component 1200 mayprovide functionality for one or more of the following actions relatedto virtual machines: create a virtual machine, update a virtual machine,delete a virtual machine, find a virtual machine, and assignment to orremoval from a standard operating environment.

A machine type may refer to a non-technical description of a computingenvironment provided by a virtual machine. Some examples of machinetypes are “C++ Developer Workstation” or “Secretarial Workstation.” Manyvirtual machines may be grouped in a single machine type. In oneembodiment, the virtual machine management component 1200 may providefunctionality for one or more of the following actions related tomachine types: creating machine types, updating a machine type, deletinga machine type, finding a machine type, and retrieving a machine type.

In some embodiments, the virtual machine management component 1200 mayprovide functionality for creating virtual machines. In one of theseembodiments, an administrator or provisioning service creates a newmachine type in a database of virtual machines. The machine type isgiven a meaningful name such as “HR Manager Workstation.” In oneembodiment, the machine type name is the name for a class of standardoperating environment (SOE) rather than a specific SOE, and multipleSOEs may be assigned to the machine type name. In another embodiment,the machine type may be used to publish the class of virtual machines.

In another of these embodiments, a standard operating environment (SOE)is created for the machine type and assigned to the machine type in thedatabase of virtual machines. In one embodiment, the SOE is a virtualmachine with a specific hardware and software configuration. A snapshotof the SOE virtual machine may be taken and used as a template forvirtual machine clones. In one embodiment, clones of the SOE virtualmachine are assigned to users.

In one embodiment, an administrator clones an SOE for use by users bycreating linked clones of the snapshot of the SOE virtual machine. Thelinked clone virtual machines may be created in consecutively numberedsubfolders in the SOE folder. The linked clones of the SOE may beassigned to the SOE in the database of virtual machines.

In another embodiment, an administrator updates a machine type bycreating a new SOE, and new linked clones of the SOE. The administratorupdates an SOE pointer within a machine type record in the database ofvirtual machines to point to the new SOE, and marks the old SOE as beingsuperseded. The administrator may create the new SOE by creating a newvirtual machine and installing the software, or by creating a full cloneof an existing SOE and updating it. As an example the administratorcould create a new virtual machine and install Microsoft Windows XPProfessional, followed by Windows XP SP1, followed by Microsoft Office2003, or the administrator could have taken a full clone of an existingSOE with Windows XP and Microsoft Office 2003 already installed, andinstalls Windows XP SP1 to achieve the same SOE. The new SOE may becreated in a new SOE folder and a new SOE record is created in thedatabase of virtual machines. Linked clones of the superseded SOE can bedeleted when users have finished with them and the superseded SOE can bedeleted when all linked clones have been deleted.

In some embodiments, a virtual machine may be designated as a sharedvirtual machine. In one of these embodiments, a shared virtual machineis an instance of a virtual machine image that is designated for use bymultiple users. In another of these embodiments, the shared virtualmachine is used by one user at a time and returned to a pool ofavailable virtual machines when not in use. In still another of theseembodiments, as the image of a shared virtual machine is executed, usersmay change the image but may not persist any changes to the image onceit is shutdown. In this embodiment, all changes are discarded when theimage is shutdown or a user terminates a session.

In other embodiments, a virtual machine may be designated as a privatevirtual machine. In one of these embodiments, a private virtual machineis an instance of a virtual machine image that is designated for use bya specific user. Only that user may be allocated to the image, launchthe image, or execute the image. In another of these embodiments,private images will be configured to permit changes to be persisted whenthe image is shutdown. In still another of these embodiments, changesmay be configured to be discarded upon image shutdown as per sharedimages, depending on the requirements of the user.

In some embodiments, a session management component is launched andidentifies a virtual machine. In one of these embodiments, the sessionmanagement component transmits an identification of a user and a virtualmachine type identified responsive to a request for access to a resourceto the virtual machine management component 1200. In another of theseembodiments, the session management component requests an identificationof a specific virtual machine to launch. In still another of theseembodiments, the session management component requests an identificationof a location of the configuration and virtual disk files of theidentified virtual machine.

In some embodiments, a virtual machine is identified responsive to thereceived identification of the user of the requesting machine. In otherembodiments, a virtual machine is identified responsive to a request bythe user for a type of virtual machine. In still other embodiments, avirtual machine is identified responsive to a request by the user for atype of computing environment.

In some embodiments, the virtual machine management component 1200transmits to the session management component an identification of aspecific virtual machine to launch. In one of these embodiments, thesession management component then proceeds to launch the virtualmachine. In another of these embodiments, the virtual machine managementcomponent launches the virtual machine.

In other embodiments, the virtual machine management component transmitsto the session management component an identification of a plurality ofvirtual machines to launch. In one of these embodiments, the sessionmanagement component may present an enumeration of available virtualmachines to a user. In another of these embodiments, the sessionmanagement component receives a selection of a virtual machine from theenumeration of available virtual machines and the session managementcomponent launches the selected virtual machine. In still otherembodiments, the virtual machine management component transmits to thesession management component an indication that no virtual machines areavailable for the user requesting the access. In yet other embodiments,the virtual machine management component 1200 transmits to the sessionmanagement component an indication that an existing, executing virtualmachine has now been allocated to the user.

In yet other embodiments, the virtual machine management componenttransmits to the session management component an identification of anavailable virtual machine responsive to accessing a database storinginformation associated with a plurality of virtual machines, theinformation including, but not limited to, an identification of theplurality of virtual machines, an identification of a location of filesassociated with the plurality of virtual machines, an identification ofan access control list associated with the plurality of virtualmachines, and an indication of availability of the plurality of virtualmachines.

In one embodiment, when a virtual machine has been identified as amachine to launch, the virtual machine management component 1200modifies an access control list associated with the virtual machineresponsive to the identification of the user received from the sessionmanagement component in the initial request. In another embodiment, thevirtual machine management component 1200 modifies the access controllist to allow the virtual machine to be launched for the user. In stillanother embodiment, the virtual machine management component 1200transmits additional information associated with the virtual machine tothe session management component. The additional information may includenetwork share details relating to a folder storing files associated withthe virtual machine. In yet another embodiment, the session managementcomponent uses the additional information to map the folder to a mountpoint, such as a drive letter, in the virtual machine.

In some embodiments, virtual machine images—configuration and data filescomprising the virtual machine—are stored on a storage area network. Inother embodiments, virtual machine images are stored in network attachedstorage. In one of these embodiments, a file server in communicationwith the storage area network makes the virtual machine imagesaccessible as if they were located on network attached storage.

Referring back to FIG. 8, an identified virtual machine is configured(step 814). In brief overview, an execution machine identified by theintermediate machine executes a hypervisor emulating hardware resourcesrequired by the requested computing environment. A session managementcomponent launches a configured virtual machine in the hypervisor.Configuration occurs of the virtual machine for a particular clientmachine 10. A connection is established between the client machine andthe virtual machine.

Referring now to FIG. 13, a block diagram depicts one embodiment of asession management component 1300 in a system providing access to acomputing environment by an intermediate machine to a requestingmachine. In brief overview, the session management component 1300includes an identification component 1302, an execution component 1304,and a management component 1306.

The identification component 1302 is in communication with a virtualmachine management component and receives an identification of a virtualmachine providing a requested computing environment. In someembodiments, the identification component 1302 is in communication withthe virtual machine management component 1200. In one embodiment, theidentification component 1302 receives an identification of an executionmachine 30′ into which to launch the virtual machine. In someembodiments, the identification component 1302 identifies an executionmachine on which a required hypervisor executes and into which to launchthe virtual machine. In other embodiments, the identification component1302 receives an identification of the execution machine. In one ofthese embodiments, the identification component 1302 receives theidentification from the intermediate machine 30.

In some embodiments, the identification component 1302 further comprisesa transceiver. In one of these embodiments, the transceiver in theidentification component 1302 receives an identification of a user ofthe requesting machine and transmits the identification of the user tothe virtual machine management component. In another of theseembodiments, the transceiver receives an identification by a user of atype of computing environment requested and transmits the identificationto the virtual machine management component 1200. In still another ofthese embodiments, the transceiver receives an identification by a userof a type of virtual machine requested and transmits the identificationof the type of virtual machine requested to the virtual machinemanagement component 1200.

In some embodiments, the identification component 1302 receives anidentification of a virtual machine providing a requested computingenvironment, the virtual machine selected responsive to a receivedidentification of a user of the requesting machine. In otherembodiments, the identification component 1302 receives anidentification of a virtual machine providing a requested computingenvironment, the virtual machine selected responsive to a receivedidentification of a type of computing environment requested. In otherembodiments, the identification component 1302 receives anidentification of a virtual machine providing a requested computingenvironment, the virtual machine selected responsive to a receivedidentification of a type of virtual machine requested.

The execution component 1304 launches the virtual machine into ahypervisor. In one embodiment, the hypervisor executes on an executionmachine 30′. In another embodiment, the execution component 1304 is incommunication with the identification component. In still anotherembodiment, the execution component 1304 receives from theidentification component 1302 an identification of an execution machine30′ executing a hypervisor into which to launches the virtual machine.In yet another embodiment, the execution component 1304 launches thevirtual machine into a hypervisor emulating hardware resources requiredto support the computing environment. In some embodiments, a virtualmachine service component executes in the hypervisor. In otherembodiments, a virtual machine service component executes in a guestoperating system provided by a virtual machine executing in thehypervisor. In one of these embodiments, the virtual machine servicecomponent is in communication with the session management component 1300and receives configuration information associated with the clientmachine 10.

The management component 1306 establishes a connection between therequesting machine and the virtual machine and manages the connection.In one embodiment, the management component 1306 provides an internetprotocol address associated with the virtual machine to the user of therequesting machine. In another embodiment, the management component 1306provides an internet protocol address associated with an executionmachine to the user of the requesting machine. In still anotherembodiment, the management component 1306 provides a proxy forcommunication between the requesting machine and the virtual machine. Inyet another embodiment, the management component 1306 establishes aconnection between the requesting machine and the virtual machine usinga presentation layer protocol.

Although described above as separate functional entities, it should beunderstood that the identification component 1302, the executioncomponents 1304 and the management component 1306 may be provided as asingle functional unit or the functions provided by those components maybe grouped into two or more components.

In some embodiments, the session management component 1300 establishesand manages a user's virtual machine session. In one of theseembodiments, the session management component 1300 providesfunctionality for, without limitation, locating a virtual machine,launching a hypervisor, launching a virtual machine in the hypervisor,connecting a user to the virtual machine, and managing the establishedconnection. In another of these embodiments, the session managementcomponent 1300 publishes a plurality of available virtual machines. Instill another of these embodiments, the session management component1300 provides, without limitation, enumeration into client drives,mapping of client drives to shared folders on the virtual machine,monitoring of the hypervisor, monitoring of an operating system providedby the virtual machine, and a virtual machine control panel to the user.

In one embodiment, the session management component 1300 provides avirtual machine control panel to the user. The virtual machine controlpanel may enable a user to switch to the virtual machine, power off thevirtual machine, reset the virtual machine, or suspend the virtualmachine. In some embodiments, the session management component 1300provides the virtual machine control panel only to users authorized toaccess the functionality of the virtual machine control panel.

In some embodiments, a virtual machine service component executes in thehypervisor. In one of these embodiments, the virtual machine servicecomponent is in communication with the session management component 1300and receives configuration information associated with the clientmachine 10. In another of these embodiments, the session managementcomponent 1300 creates a connection to the virtual machine servicecomponent, such as a TCP/IP connection, and communicates with thevirtual machine service component over the created connection. In stillanother of these embodiments, the session management component 1300transmits information associated with the client machine 10, such asinitialization parameters or client monitor geometry, to the virtualmachine service component.

In some embodiments, the session management component 1300 identifies afolder containing an image of the identified virtual machine. In one ofthese embodiments, the folder contains configuration and data filescomprising the virtual machine. In another of these embodiments, thesession management component 1300 mounts the folder in the executionmachine prior to launching the virtual machine. In still another ofthese embodiments, the session management component 1300 copiesdefinition data files associated with the virtual machine onto theexecution machine. The session management component 1300 may copy thedefinition data files back into the identified folder when a session iscompleted. In yet another of these embodiments, the configuration anddata files are streamed to the execution machine, as described below.

In other embodiments, the session management component 1300 enumeratesin the virtual machine a plurality of drives associated with the clientmachine 10. In one of these embodiments, the session managementcomponent 1300 creates a folder associated with each drive in theplurality of drives. In another of these embodiments, the sessionmanagement component 1300 stores a folder associated with a drive in theplurality of drives in the mounted folder containing the identifiedvirtual machine. In still another of these embodiments, an enumerationof the stored folder associated with the drive is provided to a user ofthe client machine 10. In some embodiments, a protocol stack located inthe hypervisor or in the guest operating system enables drive mappingthrough other techniques, including techniques enabled by presentationlayer protocols.

Referring now to FIG. 14, a block diagram depicts one embodiment of asystem in which a drive associated with the client machine 10 is madeavailable to a computing environment. In brief overview, the clientmachine 10 has a connection (1) to an execution machine and a connection(2) to a plurality of drives available to a user of the client machine10.

The session management component 1300 creates a folder associated witheach drive in the plurality of drives (3). In one embodiment, thesession management component 1300 stores the created folder associatedwith a drive in the plurality of drives in a virtual machine folder1002, the mounted folder containing configuration and data filesassociated with the identified virtual machine. In another embodiment,the session management component 1300 generates a list of shared foldersstored in the virtual machine folder 1002.

The session management component 1300 notifies the virtual machineservice component of the change to the virtual machine folder 1002 (4).In some embodiments, the session management component 1300 responds tochanges in the client device by rebuilding a shared folder list in thevirtual machine folder 1002. In one of these embodiments, the sessionmanagement component 1300 receives an identification of a modificationto the drive associated with the client machine 10. In another of theseembodiments, the session management component 1300 transmits anotification to the virtual machine service component identifying thechange to the virtual machine 1002.

For each folder associated with a drive in the virtual machine folder1002, the virtual machine service component provides an indication of amapped client drive to the virtual machine (5). In one embodiment, thevirtual machine service component associates the mapped client drivewith a drive letter on the virtual machine. In another embodiment, thevirtual machine service component monitors for changes to the sharedfolder list in the virtual machine folder 1002. In some embodiments, anenumeration of the stored folder associated with the drive is providedto a user of the client machine 10.

In some embodiments, the session management component 1300 enumerates inthe virtual machine a plurality of printers associated with the clientmachine 10. In one of these embodiments, the session managementcomponent 1300 accesses a printer service to acquire an authorizationlevel required to enumerate a printer in the plurality of printers.

In one embodiment, a printer associated with the client machine 10 isshared as a network printer and made accessible to the virtual machineas a network resource. In another embodiment, the virtual machinegenerates printer output using the TCP/IP and LPR protocols, and thisoutput is intercepted and transmitted to the printer associated with theclient machine 10. In still another embodiment, the virtual machinetransmits printer output to a virtualized hardware resource provided bythe hypervisor, such as a COM port on the virtual machine. The output iscaptured and transmitted to the printer associated with the clientmachine 10. In yet another embodiment, a hypervisor may provide accessto a virtual printer or printer port.

Referring back to FIG. 8, as part of the configuration process, anexecution machine identified by the intermediate machine executes ahypervisor emulating hardware resources required by the requestedcomputing environment. In one embodiment, the hypervisor executes on theintermediate machine. In another embodiment, the hypervisor executes ina terminal services session executing on the intermediate machine. Instill another embodiment, the hypervisor executes on the executionmachine. In yet another embodiment, the hypervisor executes in aterminal services session executing on the execution machine. In someembodiments, the hypervisor may be executed on the client machine 10.

In one embodiment, the hypervisor provisions a plurality of hardwareresources on the execution machine for use by the requested computingenvironment. In another embodiment, the hypervisor partitions aplurality of hardware resources on the execution machine and makes thepartition available for use by the requested computing environment. Instill another embodiment, the hypervisor emulates a plurality ofhardware resources on the execution machine for use by the requestedcomputing environment. In yet another embodiment, the hypervisor maypartition hardware resources, emulate hardware resources, or provisionhardware resources, or all three. For example, a hypervisor may emulatea device (such as a graphics card, network card, and disk), partitionthe (execution time) of the CPU, and virtualize registers, storage, andunderlying devices which they use to fulfill operations on theiremulated hardware (such as RAM, and network interface cards).

In some embodiments, the session management component 1300 executes thehypervisor. In one of these embodiments, the session managementcomponent 1300 executes the hypervisor in full-screen mode. In otherembodiments, the session management component 1300 monitors execution ofthe hypervisor. In one of these embodiments, the session managementcomponent 1300 transmits a notification to the virtual machinemanagement component 1200 that the virtual machine has terminated whenthe session management component 1300 receives an indication that avirtual machine executing in the hypervisor has terminated. In anotherof these embodiments, the session management component 1300 receives anotification when the user logs out of a session.

In some embodiments, the hypervisor provides a hardware abstractionlayer between hardware on the execution machine and a computingenvironment provided by a virtual machine. In one of these embodiments,there is no operating system between the execution machine hardware andthe hypervisor. The hypervisor may be said to be executing “on baremetal.” In another of these embodiments, there is an operating systemexecuting on the execution machine, referred to as a host operatingsystem, and the hypervisor executes from within the operating system.Computing environments provided by a virtual machine may be referred toas guest operating systems.

In one embodiment, the hypervisor executes in a terminal server sessionon a host operating system on the execution machine. The hypervisor mayemulate hardware resources required by a computing environment providedby a virtual machine. The hypervisor may partition hardware and provideaccess to the partition. The hypervisor may also virtualize existinghardware, making it appear to at least one domain on the hardware as ifthat domain were the only domain accessing the hardware. In anotherembodiment, output from the computing environment, or an application orresource executing within the computing environment, is passed from thecomputing environment to a virtualized hardware resource provided by thehypervisor. In still another embodiment, the hypervisor transmits theoutput to a component such as the session management component 1300. Thesession management component 1300 may transmit the received output to aclient machine 10 from which a user accesses the computing environment.In yet another embodiment, the hypervisor redirects the output from thevirtualized hardware resource to an actual hardware resource, such as anetwork interface card.

In some embodiments, the hypervisor provides a hardware abstractionlayer and creates an environment into which a virtual machine may belaunched, the virtual machine comprised of configuration and data filescreating a computing environment, which may comprise a guest operatingsystem and application programs or other resource. In other embodiments,the hypervisor provides functionality for transmitting data directed toa virtualized hardware resource and redirecting the data to a requestingmachine via the session management component 1300. In one of theseembodiments, the communication between the session management component1300 and the hypervisor enable transmission of updates, such as audioupdates, updates associated with a graphical user interface, or updatesassociated with serial COM port input/output, from the virtual machineto the requesting machine. In another of these embodiments, thecommunication enables transmission of keyboard or mouse or audio updatesfrom the requesting machine to the virtual machine. In still another ofthese embodiments, where the hypervisor executes within a terminalserver session, the hypervisor may map terminal server drives to thecomputing environment.

Referring still to FIG. 8, a virtual machine is configured for access bya particular client machine 10. In some embodiments, the managementcomponent 1300 receives an identification of a virtual machine alreadyexecuting in the hypervisor. In other embodiments, the sessionmanagement component 1300 launches the virtual machine in thehypervisor. In one embodiment, the session management component 1300receives an identification of a folder containing configuration and datafiles comprising the virtual machine. In another embodiment, the sessionmanagement component 1300 mounts the identified folder in the executionmachine.

In some embodiments, a virtual machine service component executes in aguest operating system executing within the virtual machine. In one ofthese embodiments, the virtual machine service component is a systemservice running in a network service account. In another of theseembodiments, the virtual machine service component is configured toinitiate execution automatically upon the execution of the computingenvironment. In still another of these embodiments, the virtual machineservice component communicates with the session management component1300. In other embodiments, the virtual machine service componentexecutes in the hypervisor.

In some embodiments, a virtual machine service component executes withinthe virtual machine. In one of these embodiments, after launching thevirtual machine in the hypervisor, the session management component 1300establishes a connection, such as a TCP/IP connection, with the virtualmachine service component. In another of these embodiments, the virtualmachine service component establishes the connection. The connection maybe a single multiplexed connection between the components or multipleindependent connections.

In still another of these embodiments, the session management component1300 uses the connection to transmit configuration information to thevirtual machine service component. The configuration information may beassociated with a presentation layer protocol session executing on theclient machine 10 in which output from the virtual machine is presented.The configuration information may also include information associatedwith display settings and changes, client drive information andauthentication data.

In other embodiments, the virtual machine service component receivesinformation associated with a printer to which the requesting machinehas access. In one of these embodiments, the virtual machine servicecomponent access a network printer service to create in the virtualmachine a printer connected to the printer to which the requestingmachine has access.

In still other embodiments, the virtual machine service componenttransmits session status messages to the session management component1300. In one of these embodiments, the virtual machine service componenttransmits heartbeat messages to the session management component 1300.In another of these embodiments, the virtual machine service componenttransmits keep-alive messages to the session management component 1300,to prevent the session management component 1300 from shutting down thevirtual machine. In still another of these embodiments, the virtualmachine service component transmits a message to the session managementcomponent 1300 providing an indication that the user of the clientmachine 10 has logged off, shut down, or suspended a session with thecomputing environment. The virtual machine service component may receivethe indication of the user's activity from an authentication module.

Referring still to FIG. 8, as described above, a request for access to aresource is received (step 802), a method for providing access to theresource is identified (step 804), and a virtualized environment may beselected to provide access to a resource (step 808). In someembodiments, a client machine 10 receives the request, identifies amethod for providing access, and selects a virtualized environment toprovide access to a resource. In one of these embodiments, a mobilecomputing device connects to a client machine 10 referred to as acomputing device, which identifies a method for providing access to acomputing environment, selects a portable computing environment residingin storage on the mobile computing device and provides access to theportable computing environment.

Referring ahead to FIGS. 89A and 89B, a storage device and a computingdevice are depicted. In brief overview, the storage device stores dataassociated with a computing environment, such as a portable computingenvironment, which in some embodiments includes virtualization software,a virtual machine image, and user data. A computing device connecting tothe storage device, executing a virtual machine, and providing access tothe computing environment responsive to data stored in the storagedevice.

Still referring to FIG. 89A, and in further detail, the storage device8905 stores the portable computing environment 8920 of one or moreusers. In one embodiment, the storage device 8905 may be any type andform of hard drive, including a micro hard drive. In another embodiment,the storage device 8905 may be any type and form of portable storagedevice, such as a flash drive or USB drive, or any type and form ofportable storage medium, such as a CD or DVD. In still anotherembodiment, the storage device 8905 comprises a flash card, a memorystick, multi-media card or a secure digital card. In some embodiments,the storage device 8905 may store applications including word processingor office applications, ICA clients, RDP clients, software to establishany type and form of virtual private network (VPN) or SSL VPNconnection, software to accelerate network communications or applicationdelivery or any other type and form of application.

In one embodiment, the storage device 8905 may store a virtual machineimage. In another embodiment, the storage device 8905 may comprise atransmitter for transmitting stored data to a computing device 8910. Instill another embodiment, the storage device 8905 may comprise atransceiver for accessing stored data, transmitting stored data andreceiving data for storage. In yet another embodiment, the storagedevice 8905 may comprise stored data comprising an application programfor executing a virtual machine on a computing device.

In some embodiments, the storage device 8905 is embedded in a mobilecomputing device. In other embodiments, the storage device 8905 isconnected to a mobile computing device. In still other embodiments, thestorage device 8905 comprises a portable storage device removable from acomputing device.

The storage device 8905 stores data associated with a computingenvironment. The data may comprise a portable computing environment8920. In one embodiment, the portable computing environment 8920 isconsidered portable in that the portable computing environment 8920 maybe easily or conveniently carried and transported from one computingdevice 8910 to another computing device 8910′. In another embodiment,the portable computing environment 8920 is considered portable in thatthe computing environment may be established or executed on any suitablecomputing device 8910 with little or no changes to the computing device8910, or in a further embodiment, with little or no maintenance oradministration. In still another embodiment, the portable computingenvironment 8920 includes a plurality of files representing a desktopenvironment, or a portion thereof, of a computer system 100, which auser desires to execute on the computing device 8910. In yet anotherembodiment, the portable computing environment 8920 may represent anenvironment under which a user operates a home or office desktopcomputer. In some embodiments, the portable computing environment 8920represents one or more applications to which a user has access.

The portable computing environment 8920 may include a virtual machineimage 8925. In one embodiment, the virtual machine image 8925 comprisesa computing environment image, including any of the information, data,files, software, applications and/or operating system needed to executea computing environment 8920, including files needed to execute thecomputing environment 8920 via the virtualization software 8921. Inanother embodiment, the virtual machine image 8925 comprisesconfiguration and data files required to execute a virtual machineproviding access to a computing environment requested by a user. Instill another embodiment, the virtual machine image 8925 comprises avirtual machine image as described above.

The portable computing environment 8920 may also include user data 8930,including, without limitation, any data, information, files, software orapplications of a user. In one embodiment, the user data 8930 is storedin, or as a part of, the virtual machine image 8925. In anotherembodiment, the user data 8930 may be created, edited or provided by anysoftware, program, or application of the storage device 8905 or of thecomputing device 8910.

The portable computing environment 8920 may include virtualizationsoftware 8921. In some embodiments, the virtualization software 8921 maycomprise any suitable means or mechanisms for a user to access, readand/or write any user data 8930 included in or provided by thevirtualization software 8921 and/or virtual machine image 8925. In oneof these embodiments, the virtualization software 8921 may track, manageand synchronize the access, reading and/or writing of user data 8930during an established computing environment 8920′ with the user data8930 provided on the storage device 8905. In another of theseembodiments, the user data 8930 may only be accessed via thevirtualization software 8921 or the established computing environment8920′. In still another of these embodiments, any software, programs orapplications of the storage device 8905 may access the user data 8930when the storage device 8905 is not connected to the computing device120 or when a computing environment 8920′ is not executing. In yetanother of these embodiments, the user data 8930 may comprise data andfiles created during a session of an established computing environment8920′.

The computing device 8910 may be any type and form of computer system asdescribed in connection with FIG. 1A and FIG. 1B above. In oneembodiment, the computing device 8910 is a client machine 10 asdescribed above. In another embodiment, a connection between a computingdevice 8910 and a storage device 8905 provides a user of a clientmachine 10 with access to a requested resource. In still anotherembodiment, the computing device 8910 receives a request for access to aresource when a connection is made between the computing device 8910 andthe storage device 8905. In yet another embodiment, a method forproviding access to the resource is identified responsive to informationreceived from the storage device 8905.

In one embodiment, the computing device 8910 has a storage element 128.In another embodiment, the computing device 8910 has a network interface118′ connected to network 150. In still another embodiment, thecomputing device 8910 has a transceiver for accessing data stored in astorage device 8905 or in a computing device 8910′.

In some embodiments, the computing device 8910 comprises an operationalor performance characteristic not provided by the storage device 8905.In one of these embodiments, the computing device 8910 compriseselements, such as a processor or a memory, which the storage device 8905does not include. In another of these embodiments, the computing device8910 provides an I/O device, display device, installation medium, orother peripherals, such as a keyboard or printer not available to thestorage device 8905. In still another of these embodiments, thecomputing device 8910 may provide a feature, a resource, or peripheraldesired to be used by the user of the storage device 8905. For example,the user may want to access a file or an application provided on aremote machine 30′ available via a connection across the network 150. Inyet another of these embodiments, the computing device 8910 providesaccess to a network, such as machine farm 38, not available to thestorage device 8905, or to a user of the storage device 8905.

In one embodiment, the computing device 8910 establishes a computingenvironment 8920′ based on the portable computing environment 8920provided by the storage device 8905. The computing device 8910establishes a virtual machine 8925′ and a virtualization layer 8922 toexecute the computing environment 8920′ based on the virtualizationsoftware 8921 or 8921′, virtual machine image 8925 and/or user data 230.

In some embodiments, virtualization allows multiple virtual machines8925′, with heterogeneous operating systems to run in isolation,side-by-side on the same physical machine 8910. In one embodiment, thevirtualization software 8921 may include a virtual machine image.Virtual machines may include cross-platform X86 PC emulators, such asthe products distributed by The Bochs Project at bochs.sourceforge.net,or VMware products manufactured and distributed by VMware, Inc. of PaloAlto, Calif., or products manufactured and distributed by Softricity,Inc., or the Virtuozzo products manufactured and distributed by SWSoft,Inc. of Herndon, Va., or the Microsoft® Virtual PC products manufacturedand distributed by Microsoft Corporation of Redmond, Wash. In anotherembodiment, the virtualization software 8921 includes any the AppStreamproducts manufactured and distributed by AppStream Inc, of Palo Alto,Calif., or the AppExpress products manufactured and distributed byStream Theory, Inc of Irvine, Calif.

The computing device 8910 may use any other computing resources ofcomputer system 100 b required by the computing environment 8920′. Insome embodiments, the hypervisor 8923 provides a virtualized hardwareresource required by the computing environment 8920′. In otherembodiments, a hypervisor 8923 provides, via a virtualization layer8922, access to a hardware resource required for execution of acomputing environment. In one of these embodiments, the hypervisor 8923provisions the hardware resource. In another of these embodiments, thehypervisor 8923 virtualizes the hardware resource. In still another ofthese embodiments, the hypervisor 8923 partitions existing hardwareresources and provides access to a partitioned hardware resource.

In some embodiments, a virtual machine 8925′ executing on avirtualization layer provides access to a computing environment 8920′.In other embodiments, a session management component 1300 executes thevirtual machine 8925. In still other embodiments, virtualizationsoftware 8921 or 8921′ execute the virtual machine 8925. In one of theseembodiments, the portable computing environment 8920 includes any typeand form of software for virtualizing on a computing device auser-accessible resource, such as an operating system, desktop,application, and any hardware computing resources. In yet otherembodiments, virtual machine image 8925 is accessed to execute a virtualmachine 8925′. In one of these embodiments, the virtualization software8921 or 8921′ accesses the virtual machine image.

In some embodiments, the virtualization software 8921 may includesoftware for virtualizing a server, such as the Microsoft Virtual Serverproducts manufactured and distributed by Microsoft Corporation ofRedmond, Wash., or the Linux Vserver products distributed by the LinuxVserver Project located at linux-vserver.org. In other embodiments, thevirtualization software 8921 may also include an interpreter orjust-in-time compiler, such as the JAVA Virtual Machine (JVM) originallymanufactured by Sun Microsystems of Santa Clara, Calif., or the CommonLanguage Runtime (CLR) interpreter manufactured by the MicrosoftCorporation.

In some embodiments, the computing device 8910 has the virtualizationsoftware 8921′ stored or installed in storage element 128 prior to aconnection with the storage device 8905. In one embodiment, thevirtualization software 8921′ does not need to be installed on thecomputing device 8910, and can, instead, be executed from the storagedevice 8905. In another embodiment, the computing device 8910 installsand executes the virtualization software 8921 on a per connection basis.In this embodiment, the computing device 8910 may remove thevirtualization software 8921 from storage element 128 upon terminationof the established computing environment 8920′. In still anotherembodiment, the computing device 8910 installs and executes thevirtualization software 8921 on a first connection. In yet embodiment,upon other connections, if the computing device 8910 detects changes tothe virtualization software 8921, such as a newer version, the computingdevice 8910 updates the virtualization software 8921, or installs anewer version of the virtualization software 8921. In other embodiments,the computing device 8910 obtains the virtualization software 8921 froma storage element 128″ or a remote machine 30 accessible via network150.

In one embodiment, the virtualization software 8921 is used to establisha virtualization layer 8922 on the computing device 8910. In anotherembodiment, the virtualization layer 8922 provides an abstraction layerthat decouples or isolates an application or a hardware resource fromthe operating system. In still another embodiment, the virtualizationlayer 8922 comprises an application to host or run another operatingsystem or application, such as virtual machine 8925.

In some embodiments, the hypervisor 8923 comprises the virtualizationsoftware 8921. In other embodiments, the session management component1300 comprises the virtualization software 8921. In still otherembodiments, the host computing device 8910 stores virtualizationsoftware 8921′ in storage element 128. In yet other embodiments, thecomputing device 8910 accesses a remotely located copy of virtualizationsoftware 8921′.

In some embodiments, the virtualization layer 8922 and/or virtualmachine 8925 provide an execution environment on the computing device8910. In one of these embodiments, each execution environment is aunique instance of the same execution environment, while, in another ofthese embodiments, each execution environment may be an instance ofdifferent execution environments. Each execution environment may beisolated from and/or not accessible by another execution environment. Inother embodiments, the virtualization layer 8922 and/or virtual machine8925 provides an execution context, space or “sandbox” to isolateprocesses and tasks running on the same operating system.

In one embodiment, the virtualization layer 8922 communicates with asession management component 1300. In some embodiments, the sessionmanagement component 1300 is software executing in a layer between ahypervisor 8923 or operating system of the computing device 8910 and oneor more virtual machines 8925 that provide a virtual machine abstractionto guest operating systems. In other embodiments, as described above,the session management component 1300 may reside outside of thecomputing device 8910 and be in communication with a hypervisor 8923 oroperating system of the computing device 8910. In still otherembodiment, the session management component 1300 can load, run oroperate the virtual machine image 8925 from the storage device 8905 toexecute a virtual machine 8925′. In yet other embodiments, the sessionmanagement component 1300 and hypervisor 8923 are incorporated into thesame application, software or other executable instructions to providethe virtualization layer 8922. In further embodiments, the sessionmanagement component 1300 is in communication with a virtual machineservice component executing within the computing environment 8920.

In some embodiments and still referring to FIG. 89A, the computingdevice 8910 includes a loading mechanism 8940, which may comprisesoftware, hardware, or any combination of software and hardware. In oneembodiment, the loading mechanism 8940 comprises an autorunconfiguration file. In another embodiment, the storage device 8905 mayinclude the loading mechanism 8940. In still another embodiment, thestorage device 8905 includes the loading mechanism 8940 in an autorunfile. In some embodiments, a loading mechanism 8940 on the storagedevice 8905 establishes the computing environment 8920′ on the computingdevice 8910 based on the portable computing environment 8920 stored inthe storage device 8905. In other embodiments, the loading mechanism8940′ of the computing device 8910 establishes of the computingenvironment 8920′. In still other embodiments, the loading mechanism8940 of the storage device 8905 works in conjunction with the loadingmechanism 8940′ of the computing device 8910 to establish the computingenvironment 8920′.

In one embodiment, the loading mechanism 8940 comprises a driver, suchas a device driver or a kernel or user-mode driver for connecting toand/or accessing the storage device 8905, or the storage element 128thereof. In another embodiment, the loading mechanism 8940 comprises anytype and form of executable instructions, such as a program, library,application, service, process, thread or task for accessing the storageelement 128 or storage device 8905. In still another embodiment, theloading mechanism 8940 accesses any type and form of data andinformation on the storage 128 to establish the user environment 8920′in accordance with the operations discussed herein. For example, in someembodiments, the loading mechanism 8940 reads an autorun configurationfile in storage element 128 or on storage device 8905. In someembodiments, the loading mechanism 8940 comprises a plug-n-play (PnP)mechanism by which the operating system of the host computing device8910 recognizes the storage device 8905 upon connection, and loads thedrivers to connect to the storage device 8905.

In one embodiment, the loading mechanism 8940 upon detection of aconnection between the storage device 8905 and computing device 8910initiates the loading, establishing and/or executing of thevirtualization software 8921 and/or the user environment 8920′ on thecomputing device 8910. In another embodiment, the loading mechanism 8940may comprise any rules, logic, operations and/or functions regarding theauthentication and/or authorization of establishing a computingenvironment 8920′ on the computing device 8910 based on the portablecomputing environment 8920. In still another embodiment, the loadingmechanism 8940 may determine the existence of the virtualizationsoftware 8921′ on the computing device 8910 and/or the difference inversions between the virtualization software 8921 and virtualizationsoftware 8921′. In yet another embodiment, the loading mechanism 8940may store, load, and/or execute the virtualization software 8921 or8921′ on the computing device 8910. In a further embodiment, the loadingmechanism 8940 may store, load, and/or execute the virtual machine image8925 on the computing device 8910 as a virtual machine 8925 providingaccess to the computing environment 8920′. In still another embodiment,the loading mechanism 8940 may comprise or provide any type and form ofuser interface, such as graphical user interface or command lineinterface.

In some embodiments, the virtualization software 8921, portablecomputing environment 8920 and/or loading mechanism 8940 are designedand constructed in accordance with the U3 application designspecification, or USB smart drive, provided by U3 LLC of Redwood City,Calif. For example, the loading mechanism 8940 may comprise a U3launchpad program, and the virtualization software 8921 and/or portableuser environment 120 may comprise a U3-based application.

Referring now to FIG. 89B, a flow diagram depicts one embodiment of thesteps taken in a method for providing access to a computing environmenton a computing device via a storage device. In brief overview, a methodfor providing access to a computing environment includes the step ofstoring, in a storage device, data associated with a computingenvironment (step 8950). A computing device connects to the storagedevice (step 8960). A virtual machine executing on the computing deviceprovides access to the computing environment, based on the data storedin the storage device (step 8970).

In further detail, a storage device 8905 stores data associated with aportable computing environment 8920 (step 8950). In one embodiment, thestorage device 8905 stores user data associated with the computingenvironment. In another embodiment, the storage device 8905 stores avirtual machine image 8925. In still another embodiment, the storagedevice 8905 stores data associated with a computing environment, thecomputing environment comprising at least one application program. Inyet another embodiment, the storage device 8905 stores data associatedwith a computing environment, the computing environment comprising anoperating system.

In one embodiment, the storage device 8905 stores data comprising anoperating system. In another embodiment, the storage device 8905 storesdata comprising an application program. In still another embodiment, thestorage device 8905 stores an application program for executing avirtual machine on a computing device. In yet another embodiment, thestorage device 8905 stores virtualization software for executing avirtual machine on a computing device.

In some embodiments, the storage device 8905 may include a connector forestablishing a connection between the storage device 8905 and acomputing device. In other embodiments, the storage device 8905 residesin a computing device, such as a mobile computing device. In one ofthese embodiments, the storage device 8905 is embedded in a mobilecomputing device. In still other embodiments, the storage device 8905comprises a portable storage device removable from a computing device.

A computing device connects to the storage device (step 8960). Thestorage device 8905 may connect to the computing device 8910 by anysuitable means and/or mechanism. In one embodiment, the storage device8905 connects to a computing device 8910 via a mobile computing device.In another embodiment, the storage device 8905 is embedded in a mobilecomputing device connectable to the computing device 8910.

Upon connection, a request may be received by the computing device 8910for access to a resource. In one embodiment, the request is for adesktop environment. In another embodiment, the request is for anapplication or for a plurality of applications. In still anotherembodiment, the request is for a virtual machine.

In some embodiments, a determination may be made to provide access tothe requested resource via a virtualized environment. In one of theseembodiments, the determination is made as described above in connectionwith FIG. 8. In another of these embodiments, the determination is maderesponsive to information received from the storage device 8905, such asa rule requiring the determination.

In one embodiment, the computing device 8910 accesses the storage device8905 to access the portable computing environment 8920. In anotherembodiment, the computing device 8910 obtains the virtualizationsoftware 8921 from the storage device 8905 to establish a computingenvironment 8920′. In still another embodiment, the computing device8910 does not obtain the virtualization software 8921 from the storagedevice 8905 as the computing device 8910 has access to thevirtualization software 8921 in storage element 128′ or via network 150.In yet another embodiment, the computing device 8910 obtains portions ofthe virtualization software 8921 from the storage device 8905. Forexample, the virtualization software 8921 on the storage device 8905 maybe an updated version or have updated files to the virtualizationsoftware 8921′ on the computing device 8910. In some embodiments, thestorage device 8905 transmits information to the computing device 8910.In one of these embodiments, the storage device 8905 transmits theinformation with a request for access to a resource.

A virtual machine executing on the computing device provides access tothe computing environment, based on the data stored in the storagedevice (step 8970). In one embodiment, the computing device 8910retrieves data from the storage device 8905. In another embodiment, thecomputing device 8910 accesses the storage device 8905 to obtain avirtual machine image 8925 used to execute the virtual machine. In stillanother embodiment, the computing device 8910 accesses the storagedevice 8905 to obtain data or information identifying a location of theportable computing environment 8920 that may be accessible to thecomputing device 8910. For example, the storage device 8905 may compriseuser data 8930 identifying a Uniform Resource Locator (URL) associatedwith a location on which a virtual machine image 8925 is stored, the URLaccessible by the computing device 8910 via network 150. In yet anotherembodiment, the computing device 8910 accesses a storage elementidentified by the user data 8930, for example, a storage element orremote machine 30 on the network 150 storing the virtual machine image8925.

In some embodiments, the computing device 8910 mounts the storage device8905 as a storage, such as a disk, available to the computing device8910. In one of these embodiments, the computing device 8910 mounts thestorage device 8905 as removable media. In other embodiments, theloading mechanism 8940 accesses the storage device 8905.

The computing device 8910 establishes an environment for executing orproviding access to the computing environment 8920′. In one embodiment,a virtual machine may be executed in the computing environment 8920′ toprovide access to a requested resource. In another embodiment, a virtualmachine is the requested resource. In still another embodiment, avirtual machine 8925′ executes a virtual machine 8925″.

In one embodiment, the computing device 8910 executes a virtual machineresponsive to a virtual machine image 8925 stored in the storage device8905. In another embodiment, the computing device 8910 executes avirtual machine 8925′ responsive to the data stored in the storagedevice 8905. In still another embodiment, the computing device 8910executes the virtual machine responsive to a policy stored in thestorage device.

In one embodiment, the computing device 8910 retrieves data stored inthe storage device 8905. In another embodiment, the computing device8910 uses an application program stored in the storage device 8905 toaccess the data. In still another embodiment, the computing device 8910provides access to a computing environment by executing an operatingsystem providing access to one or more applications identified byinformation stored in the storage device, the operating system and theone or more applications having access to user data stored in thestorage device 8905.

In one embodiment, the computing device 8910 installs and/or loads thevirtualization software 8921 to establish the virtualization layer 8922.In some embodiments, the virtualization software 8921 is designed andconstructed as a portable application that can execute, load orestablish the virtualization layer 8922 on the computing device 8910without requiring installation of the virtualization software 8921. Inother embodiments, the virtualization software 8921 is automaticallyinstalled on the computing device 8910 via an installation script. Inone of these embodiments, the virtualization software 8921 is installedwithout requiring a reboot. In another of these embodiments, thevirtualization software 8921 is installed and the virtualization layer8922 established transparently to a user. In still other embodiments,the virtualization layer 8922 is established using the virtualizationsoftware 8921′ stored on the computing device 8910 or accessed vianetwork 150.

In some embodiments, the computing device 8910 executes a hypervisor8923 to establish the virtualization layer 8922. In other embodiments, ahypervisor 8923 on the computing device 8910 and in communication with ahypervisor 8923′ on a remote machine 30′ establishes the virtualizationlayer 8922. In still other embodiments, a hypervisor 8923 incommunication with a session management component 1300 establishes thevirtualization layer 8922. In one of these embodiments, uponestablishment of the virtualization layer 8922, the session managementcomponent 1300 identifies, provisions, and/or executes a virtual machinein the virtualization layer 8922 as described above in connection withFIG. 8. In yet other embodiments, the loading mechanism 8940 establishesthe virtualization layer 8922. In further embodiments, the computingdevice 8910 establishes a virtualization layer 8922 in which a virtualmachine service component executes.

In one embodiment, the virtualization layer 8922 has been establishedprior to the storage device 8905 connecting to the computing device8910. For example, the virtualization layer 8922 may have beenestablished for another computing environment 8920′ or during a previousconnection of the same or a different storage device 8905. In someembodiments, the computing device 8910 and/or loading mechanism 8940establishes the virtualization layer 8922 and actuates, starts, orexecutes a session management component 1300 and/or hypervisor 8923. Inother embodiments, the computing device 8910 and/or loading mechanism8940 executes session management component 1300 and/or hypervisor 8923upon loading or executing a virtual machine 8925.

The computing device 8910 provides access to the computing environment8920′ based on the portable computing environment 8920 (step 8970). Inone embodiment, the computing device 8910 and/or loading mechanism 8940accesses the virtual machine image 8925 from storage device 8905 andexecutes the virtual machine image 8925 as a virtual machine 8925′ inthe established virtualized environment 8922. In another embodiment, thecomputing device 8910 and/or loading mechanism 8940 automatically loads,executes or otherwise establishes the computing environment 8920 withthe virtualization layer 8922 upon detection of a connection overnetwork 150. In still another embodiment, the computing device 8910and/or loading mechanism 8940 automatically loads, executes or otherwiseestablishes the computing environment 8920 and the virtualization layer8922 upon detection of existence or identification of the portablecomputing environment 8920 in storage element 128.

In some embodiments, a user may select the virtual machine image 8925from the storage device 8905 for execution as a virtual machine 8925′via any type and form of user interface. In one of these embodiments,the virtualization software 8921, virtualization layer 8922, hypervisor8923, or loading mechanism 8940 may display a user interface for a userto identify a virtual machine image 8925, and/or to execute a virtualmachine 8925′ based on a virtual machine image 8925. In another of theseembodiments, a client, such as an ICA client, an RDP client, or an X11client, executes on the computing device 8910 and provides the userinterface to the user.

In some embodiments, a user may access, read, and/or write user data8930 during the course of using the established computing environment8920′. In one of these embodiments, a user of the computing device 8910may access, read and/or write the user data 8930 to the storage device8905. In another of these embodiments, a user of the computing device8910 may edit or modify user data 8930 or may create new data andinformation in user data 8930.

In other embodiments, a user of the computing device 8910 may access,read, and/or write user data to the storage 128′ of the computing device8910. In still other embodiments, the computing device 8910 maysynchronize user data 8930 on the computing device 8910 with user data8930 on the storage device 8905. In one of these embodiments, thecomputing device 8910 uses the virtualization layer 8922 or the loadingmechanism 8940 to synchronize the user data 8930. In yet otherembodiments, the storage device 8905 may have a program or applicationfor synchronizing data between the storage device 8905 and the computingdevice 8910.

In some embodiments, the storage device 8905 may disconnect from thecomputing device 8910 at any point in time during the establishedcomputing environment 8920′. In other embodiments, the storage device8905 may disconnect after the computing environment 8920′ is terminatedon the computing device 8910. In still other embodiments, the computingenvironment 8920′ is automatically terminated upon disconnection of thestorage device 8905 to the computing device 8910. In yet otherembodiments, the computing environment 8920′ may remain established onthe computing device 8910 after the storage device 8905 disconnects fromthe computing device 8910. In one of these embodiments, once thecomputing environment 8920′ is established on the computing device 8910,the storage device 8905 may be disconnected.

In some embodiments, the storage device 8905 can access, read, and/orwrite user data 8930 to any portion of the portable computingenvironment 8920. In one of these embodiments, although the portablecomputing environment 8920 is not established or virtualized oncomputing device 8910, the storage device 8905 can still access, read,and/or write to and from the user data 8930. In other embodiments, auser may use a first application in the established computingenvironment 8920′ to access a file of the user data 8930. In still otherembodiments, the user may use a second application on the storage device8905 to access the same file of the user data 8930. In yet otherembodiments, the virtualization software 8921 or virtual image 8925allows access to the user data 8930, even though virtualization software8921 or virtual machine image 8925 is not executing or operating.

Although FIGS. 89A and 89B are generally discussed with one portablecomputing environment 8920 stored in the storage device 8905, thestorage device 8905 may store a plurality of portable computingenvironments 8920 for establishing a corresponding plurality ofcomputing environments 8920′ on the computing device 8910. In someembodiments, the computing device 8910, loading mechanism 8940, or thevirtualized layer 8920 provides a user interface for the user to selecta portable computing environment from storage to establish the computingenvironment 8920. For example, the storage device 8905 or the computingdevice 8910 may have a portable computing environment selectionmechanism as is further discussed in connection with FIG. 92A and withFIG. 93A. In other embodiments, the computing device 8910, loadingmechanism 8940, or the virtualized layer 8922 uses one of the pluralityof portable computing environments based on a characteristic of thecomputing device, such as operating system type, or based on user dataidentifying the portable computing environment to use for the computingdevice.

Referring now to FIGS. 90A, a mobile computing device 9005 is depicted.In brief overview, the mobile computing device 9005 may be any type andform of computer system as described in connection with FIG. 1A and FIG.1B above. In one embodiment, the mobile computing device 9005 comprisesa storage device, such as a storage device 8905 as described inconnection with FIG. 89A and FIG. 89B. In another embodiment, the mobilecomputing device 9005 is connected to a storage device 8905. In stillanother embodiment, the mobile computing device 9005 comprises aportable storage device removable from a computing device. In yetanother embodiment, the mobile computing device 9005 has a networkinterface 118 used to connect to remote machines 30 or client machines10 on the network 150, such as the computing device 8910. The storagedevice 8905 may store a portable computing environment 8920, which insome embodiments includes virtualization software 8921, a virtual image8925, and user data 8930.

In some embodiments, the mobile computing device 9005 stores dataassociated with a computing environment, executes a virtual machine, andprovides access to the computing environment responsive to data storedin the mobile computing device 9005. In one of these embodiments, themobile computing device 9005 comprises a stored virtual machine image.In another of these embodiments, the mobile computing device 9005comprises an application program for executing a virtual machine on acomputing device. In still another of these embodiments, the mobilecomputing device 9005 provides access to a computing environment byexecuting an operating system with access to one or more applicationsidentified via data stored on the mobile computing device, the operatingsystem and the one or more applications having access to the user dataon the mobile computing device. In other embodiments, the mobilecomputing device 9005 stores the portable computing environment 8920 ofone or more users in storage provided by a storage device, such as astorage device 8905 as described above in connection with FIG. 89A and89B.

In one embodiment, the mobile computing device 9005 decrypts storeddata. In another embodiment, the mobile computing device 9005 preventsone of unauthenticated and unauthorized access by a user of the mobilecomputing device 9005 to a computing environment provided by the mobilecomputing device 9005.

Referring now to FIG. 90B, a flow diagram depicts one embodiment of thesteps taken in a method for providing a computing environment by amobile computing device. In brief overview, a method includes the stepof storing, in a mobile computing device 9005, data associated with acomputing environment (step 9020). A virtual machine executing on themobile computing device provides access to the computing environment,based on the stored data (step 9025).

In further detail, the mobile computing device 9005 stores dataassociated with a computing environment (step 9020). In one embodiment,the mobile computing device 9005 receives the data associated with thecomputing device from a storage device connected to the mobile computingdevice 9005. In another embodiment, the mobile computing device storesthe data associated with the computing environment in a storage device8905 embedded in the mobile computing device. In still anotherembodiment, the mobile computing device 9005 stores user data associatedwith the computing environment. In yet another embodiment, the mobilecomputing device 9005 stores a virtual machine image.

In one embodiment, the mobile computing device 9005 stores dataassociated with a computing environment, the computing environmentcomprising at least one application program. In another embodiment, themobile computing device 9005 stores data associated with a computingenvironment, the computing environment comprising an operating system.In still another embodiment, the mobile computing device 9005 storesdata comprising an operating system. In yet another embodiment, themobile computing device 9005 stores data comprising an applicationprogram. In some embodiments, the mobile computing device 9005 stores anapplication program for executing a virtual machine. In otherembodiments, the mobile computing device 9005 stores virtualizationsoftware for executing a virtual machine.

In some embodiments, a request may be received by the mobile computingdevice 9005 for access to a resource. In one of these embodiments, therequest is for a desktop environment. In another of these embodiments,the request is for an application or for a plurality of applications. Instill another of these embodiments, the request is for a virtualmachine. In yet another of these embodiments, the request is for accessto a computing environment.

In some embodiments, a determination may be made to provide access tothe requested resource via a virtualized environment. In one of theseembodiments, the determination is made as described above in connectionwith FIG. 8. In another of these embodiments, the determination is maderesponsive to information received from the mobile computing device9005, such as a rule requiring the determination.

A virtual machine executing on the mobile computing device providesaccess to the computing environment, based on the stored data (step9025). In one embodiment, an application program stored in the mobilecomputing device 9005 executes to access data associated with thecomputing environment. In another embodiment, the mobile computingdevice 9005 executes virtualization software, at least a portion ofwhich is stored on the mobile computing device 9005. In still anotherembodiment, the mobile computing device 9005 provides access to acomputing environment by executing an operating system with access toone or more applications stored on the mobile computing device, theoperating system and the one or more applications having access to userdata stored in the mobile computing device 9005.

In one embodiment, the mobile computing device 9005 executes a virtualmachine, responsive to data stored in the mobile computing device 9005.In another embodiment, the mobile computing device executes a virtualmachine responsive to a policy stored in the mobile computing device9005. In still another embodiment, the mobile computing device 9005executes a virtual machine that provides access to a requested resourceor computing environment, the virtual machine executed responsive to avirtual machine image stored in the mobile computing device 9005. In yetanother embodiment, the mobile computing device 9005 transfers executionof the virtual machine to a computing device 8910.

Although FIGS. 90A and 90B are generally discussed with one portableuser environment 8920 stored in storage 8905 of the mobile computingdevice 9005, the mobile computing device 9005 may store a plurality ofportable computing environments 8920 for establishing a correspondingplurality of computing environments 8920′ on the mobile computing device9005.

Referring now to FIG. 91A, a mobile computing device and a computingdevice are depicted. In brief overview, the mobile computing devicestores data associated with a computing environment. The computingdevice connects to the mobile computing device, executes a virtualmachine, and provides access to the computing environment responsive todata stored in the mobile computing device. In one embodiment, thevirtual machine executing on the computing device provides access to thecomputing environment.

In one embodiment, the mobile computing device 9005 may be any type andform of computer system as described in connection with FIG. 1A and FIG.1B above. In another embodiment, the mobile computing device 9005comprises a storage device 8905 as described above in connection withFIG. 90A and FIG. 90B. In another embodiment, the mobile computingdevice may be a mobile computing device 9005 as described above inconnection with FIG. 90A and FIG. 90B. In some embodiments, the mobilecomputing device 9005 provides access to a portable computingenvironment 8920 of one or more users in storage provided by a storagedevice, such as a storage device 8905 as described above in connectionwith FIG. 89A and 89B.

In some embodiments, the mobile computing device 9005 and the computingdevice 8910 may have the same processor or computer architecture, suchas an X86 based processor architecture. In other embodiments, the mobilecomputing device 9005 may have a different processor or architecturethan the computing device 8910. For example, the computing device 8910may be a SPARC (Scalable Processor Architecture) and the mobilecomputing device 9005 may be an ARM based architecture. In someembodiments, the mobile computing device 9005 and the computing device8910 may both operate a processor, or a data address or bus using thesame numbers of bits, such as a 32-bit or 64-bit processor or bus. Inother embodiments, the mobile computing device 9005 and the computingdevice 8910 may operate on processors and/or a data bus with differentbit architectures. Furthermore, the mobile computing device 9005 andcomputing device 8910 may operate the same operating system, in oneembodiment, and different operating systems, in another embodiment. Forexample, the mobile computing device 9005 may operate a PALM operatingsystem while the computing device 8910 runs a WINDOWS operating system.

In one embodiment, a mobile computing device 9005 has multipleprocessors. One processor may have higher performance characteristicsthan the other processor, and each processor may share one or morestorage and memory elements. For example, a storage element, such as adisk drive or portable storage device, may include a computingenvironment. The mobile computing device 9005 may also have a switchingmechanism to switch between using a first processor having higherperformance characteristics and a second processor having lowerperformance characteristics, based on operating conditions andapplications executing on the device. The processor having lowerperformance characteristics may be used to execute applications withlower power requirements, such as typical PDA functionality of calendaraccess and email. When an application requires more power, the mobilecomputing device 9005 may automatically switch execution of suchapplications to the more powerful processor.

The computing device 8910 connects to the mobile computing device,executes a virtual machine, and provides access to the computingenvironment responsive to data stored in the mobile computing device9005. In one embodiment, the computing device 8910 may mount the storagedevice 8905 of the mobile computing device 9005 as a removable harddrive or storage element 128′ of the computing device 8910. In someembodiments, the mobile computing device 9005 may be a plug and playdevice (PnP) of the computing device 8910, such that a PnP protocolmanufactured by Microsoft Corporation of Redmond, Wash., is used betweenthe mobile computing device 9005 and computing device 8910, such as viaI/O devices 130 a-130 n or network interfaces 118, 118′.

In some embodiments, the computing device 8910 comprises an operationalor performance characteristic not provided by the mobile computingdevice 9005. In one of these embodiments, the computing device 8910 hasa more powerful processor 102′ and/or larger memory 122′ than theprocessor 102 and memory 122 of the mobile computing device 9005. Inanother of these embodiments, the computing device 8910 provides an I/Odevice 130 b, display device, installation medium, or other peripherals,such as a keyboard or printer not available to the mobile computingdevice 9005. In still another of these embodiments, the computing device8910 may provide a feature, a resource, or peripheral desired to be usedby the user of the mobile computing device 9005. For example, the usermay want to access a file or an application provided on a remote machine30′ available via a connection across the network 150. In yet another ofthese embodiments, the computing device 8910 provides access to machineson a network 150, such as those in machine farm 38, not available to themobile computing device 9005, or to a user of the mobile computingdevice.

In one embodiment, the computing device 8910 provides access to acomputing environment 8920′ based on the portable computing environment8920 provided in the mobile computing device 9005. The computing device8910 executes a virtual machine 8925′ and a virtualization layer 8922 toexecute the computing environment 8920′ based on the virtualizationsoftware 8921 or 8921′, virtual machine image 8925, or user data 230. Insome embodiments, the computing device comprises a transceiver foraccessing data stored in the mobile computing device 9005.

In some embodiments, a loading mechanism on the mobile computing device9005 actuates the establishment of the computing environment 8920′ onthe computing device 8910 based on the portable computing environment8920 stored in the mobile computing device 9005. In other embodiments,the loading mechanism 8940 of the computing device 8910 actuates theestablishment of the computing environment 8920′. In yet anotherembodiment, a loading mechanism on the mobile computing device 9005works in conjunction with the loading mechanism 8940 of the computingdevice 8910 to establish the computing environment 8920′.

Referring now to FIG. 91B, a flow diagram depicts one embodiment of thesteps taken in a method for providing access to a computing environmenton a computing device via a mobile computing device. In brief overview,a method includes the step of storing, in a mobile computing device,data associated with a computing environment (step 9155). A computingdevice connects to the mobile computing device (step 9160). A virtualmachine executing on the computing device provides access to a computingenvironment, based on the data stored in the mobile computing device(step 9165).

A mobile computing device stores data associated with a computingenvironment (step 9155). In one embodiment, the mobile computing device9005 may store data associated with a computing environment as describedabove in connection with FIG. 90A and 90B. In one embodiment, the mobilecomputing device 9005 may comprise a storage device embedded in themobile computing device 9005, such as the storage device 8905 describedin connection with FIG. 89A through FIG. 90B.

The computing device 8910 connects to the mobile computing device 9005by any suitable means and/or mechanism (step 9160). In one embodiment,the computing device 8910 connects to a storage device, such as astorage device 8905 as described above in connection with FIG. 89A andFIG. 89B, via the mobile computing device 9005. Upon connection, arequest may be received by the computing device 8910 for access to aresource. In one embodiment, the request is for access to a desktopenvironment. In another embodiment, the request is for an application orfor a plurality of applications. In still another embodiment, therequest is for a virtual machine. In some embodiments, a determinationmay be made to provide access to the requested resource via avirtualized environment. In one of these embodiments, the determinationis made as described above in connection with FIG. 8. In another ofthese embodiments, the determination is made responsive to informationreceived from the mobile computing device 9005, such as a rule requiringthe determination.

In one embodiment, the computing device 8910 accesses the mobilecomputing device 9005 to obtain the portable user environment 8920. Inanother embodiment, the computing device 8910 obtains the virtualizationsoftware 8921 to establish the virtualized environment 8922. In stillanother embodiment, the computing device 8910 does not obtain thevirtualization software 8921 from the mobile computing device 9005 asthe computing device 8910 has access to the virtualization software 8921in storage element 128′ or via network 150. In yet another embodiment,the computing device 8910 obtains portions of the virtualizationsoftware 8921 from the mobile computing device 9005. For example, thevirtualization software 8921 on the mobile computing device 9005 may bean updated version or have updated files to the virtualization software8921′ on the computing device 8910. In some embodiments, the mobilecomputing device 9005 transmits information to the computing device8910. In one of these embodiments, the mobile computing device 9005transmits the information with a request for access to a resource.

In one embodiment, the computing device 8910 accesses the mobilecomputing device 9005 to obtain the virtual machine image 8925. Inanother embodiment, the computing device 8910 accesses the mobilecomputing device 9005 to obtain data or information identifying alocation of the portable user environment 8920 in any storage that maybe accessible to the computing device 8910. For example, the mobilecomputing device 9005 may comprise user data 8930 identifying a UniformResource Locator (URL) associated with a location on which a virtualmachine image 8925 is stored, the URL accessible by the computing device8910 via network 150. In still another embodiment, the computing device8910 accesses a storage element identified by the user data 8930, forexample, a storage element on network 150 storing the virtual machineimage 8925. In some embodiments, the computing device 8910 mounts themobile computing device 9005 as a storage element, such as a disk,available to the computing device 8910. For example, in one embodiment,the computing device 8910 mounts the mobile computing device 9005 asremovable media. In one embodiment, the loading mechanism 8940 accessesthe mobile computing device 8905.

In some embodiments, the computing device 8910 provides access to acomputing environment by executing an operating system with access toone or more applications identified via data stored on the mobilecomputing device, the operating system and the one or more applicationshaving access to the user data on the storage device. In otherembodiments, the computing device prevents one of unauthenticated orunauthorized access by a user of the mobile computing device 9005 to acomputing environment provided by the computing device 8910. In stillother embodiments, the computing device 8910 decrypts data stored on themobile computing device 9005.

A virtual machine executing on the computing device 8910 provides accessto a computing environment, based on data stored in the mobile computingdevice 9005 (step 9165). In one embodiment, the computing device 8910establishes a virtualized environment for providing access to thecomputing environment 8920′ by executing the virtual machine 8925. Inanother embodiment, a virtual machine may be executed in the userenvironment 8920′ to provide access to a requested resource. In stillanother embodiment, a virtual machine is the requested resource. In someembodiments, the computing device 8910 executes a virtual machineresponsive to a virtual machine image 8925 stored in the mobilecomputing device 9005. In other embodiments, the computing device 8910executes a virtual machine responsive to data stored in the mobilecomputing device 9005.

In one embodiment, an application program stored in the mobile computingdevice 9005 is executed to access data associated with a computingenvironment. In another embodiment, the computing device 8910 executesvirtualization software 8921′ by accessing at least a portion of thevirtualization software 8921 stored in the mobile computing device 9005.

In one embodiment, the computing device 8910 executes the virtualizationsoftware 8921 to establish the virtualization layer 8922. In someembodiments, the virtualization software 8921 is automatically installedon the host computing device 8910 via an installation script. In one ofthese embodiments, the virtualization software 8921 is installed withoutrequiring a reboot. In another of these embodiments, the virtualizationsoftware 8921 is installed and the virtualization layer 8922 establishedtransparently to a user.

In some embodiments, the computing device 8910 executes a hypervisor8923 to establish the virtualization layer 8922. In other embodiments, ahypervisor 8923 on the computing device 8910 and in communication with ahypervisor 8923′ on a remote machine 30′ establishes the virtualizationlayer 8922. In still other embodiments, a hypervisor 8923 incommunication with a session management component 1300 establishes thevirtualization layer 8922. In one of these embodiments, uponestablishment of the virtualization layer 8922, the session managementcomponent 1300 identifies, provisions, and/or executes a virtual machinein the virtualization layer 8922 as described above in connection withFIG. 8. In yet other embodiments, the loading mechanism 8940 establishesthe virtualization layer 8922. In one embodiment, the computing device8910 establishes a virtualization layer 8922 in which a virtual machineservice component executes.

In one embodiment, the virtualization layer 8922 has been establishedprior to the mobile device 9005 connecting to the computing device 8910.For example, the virtualization layer 8922 may have been established foranother user environment 8920′ or during a previous connection of thesame or different mobile computing device 9005. In some embodiments, thecomputing device 8910 and/or loading mechanism 8940 establishes thevirtualization layer 8922 and actuates, starts, or executes a sessionmanagement component 1300 and/or hypervisor 8923. In other embodiments,the computing device 8910 and/or loading mechanism 8940 executes thesession management component 1300 and/or hypervisor 8923 upon loading orexecuting a virtual machine 8925.

In some embodiments, the computing device 8910 establishes, executes orotherwise provides the computing environment 8920′ based on the portablecomputing environment 8920. In one embodiment, the computing device 8910and/or loading mechanism 8940 accesses the virtual image 8925 from themobile computing device 9005 and loads or executes the virtual machineimage 8925 as a virtual machine 8925 in the established virtualizedenvironment 8922. In another embodiment, the computing device 8910and/or loading mechanism 8940 automatically loads, executes or otherwiseestablishes the computing environment 8920 with the virtualization layer8922 upon detection of a connection over network 150. In still anotherembodiment, the computing device 8910 and/or loading mechanism 8940automatically loads, executes or otherwise establishes the computingenvironment 8920 and the virtualization layer 8922 upon detection ofexistence or identification of the portable computing environment 8920on the mobile computing device 9005.

In some embodiments, a user may select the virtual machine image 8925from the mobile computing device 9005 for execution as a virtual machine8925 via any type and form of user interface. In one of theseembodiments, the virtualization software 8921, virtualization layer8922, hypervisor 8923, or loading mechanism 8940 may display a userinterface for a user to identify a virtual image 8925, and/or to executea virtual machine 8925 based on a virtual image 8925. In another ofthese embodiments, a client, such as an ICA client, an RDP client, or anX11 client, executes on the computing device 8910 and provides the userinterface to the user.

In some embodiments, a user may access, read, and/or write user data8930 during the course of using the established user environment 8920′.In one of these embodiments, the user host computing device 8910 mayaccess, read and/or write the user data 8930 to the mobile computingdevice 9005. In another of these embodiments, the user of the computingdevice 8910 may edit or modify user data 8930 or may create new data andinformation in user data 8930.

In other embodiments, a user of the computing device 8910 may access,read, and/or write user data to the storage element 128′ of thecomputing device 8910. In still other embodiments, the computing device8910 may synchronize user data 8930 on the computing device 8910 withuser data 8930 on the mobile computing device 8905. In one of theseembodiments, the computing device 8910 uses the virtualization layer8922 or the loading mechanism 8940 to synchronize the user data 8930. Inyet other embodiments, the mobile computing device 9005 may have aprogram or application for synchronizing data, such as files andfolders, between the mobile computing device 9005 and the computingdevice 8910.

In one embodiment, the mobile computing device 9005 may disconnect fromthe computing device 8910. In some embodiments, the mobile computingdevice 9005 may disconnect at any point in time during the use of theestablished computing environment 8920′. In other embodiments, themobile computing device 9005 may disconnect after the computingenvironment 8920′ is terminated on the computing device 8910. In stillother embodiments, the user environment 8920′ is automaticallyterminated upon disconnection of the mobile computing device 9005 fromthe computing device 8910. In one embodiment, the computing environment8920′ may remain established on the computing device 8910 after themobile computing device 9005 disconnects from the computing device 8910.In some embodiments, once the computing environment 8920′ is establishedon the computing device 8910, the mobile computing device 9005 may bedisconnected.

In some embodiments, the mobile computing device 9005 can access, read,and/or write user data 8930 to any portion of the portable computingenvironment 8920. For example, in one embodiment, although the portablecomputing environment 8920 is not established or virtualized oncomputing device 8910, the mobile computing device 9005 can stillaccess, read, and/or write to and from the user data 8930. In oneembodiment, the user may use a first application in the establishedcomputing environment 8920′ to access a file of the user data 8930. Inanother embodiment, the user may use a second application on the mobilecomputing device 9005 to access the same file of the user data 8930. Insome embodiments, the virtualization software 8921 or virtual machineimage 8925 allows access to the user data 8930, even thoughvirtualization software 8921 or virtual image 8925 is not executing oroperating.

In some embodiments, the computing device 8910, loading mechanism 8940,or the virtualized layer 8920 provides a user interface for the user toselect a portable computing environment from storage to establish thecomputing environment 8920. For example, the mobile computing device9005 or the computing device 8910 may have a portable computingenvironment selection mechanism, as discussed in greater detail below.In other embodiments, the computing device 8910, loading mechanism 8940,or the virtualized layer 8922 uses one of the plurality of portablecomputing environments based on a characteristic of the computing device8910, such as an operating system type, or based on user dataidentifying the portable computing environment to use for the computingdevice 8910.

Referring now to FIG. 92A, in one embodiment, the computing device 8910further comprises a computing environment selector 9250. In briefoverview, FIG. 92A depicts a mobile computing device 9005 connected to acomputing device 8910 via a network 150. The mobile computing device9005 further comprises a storage element 128, an I/O device or interface130, and a loading mechanism 8940. The mobile computing device 9005stores one or more portable computing environments 8920 a-8920 n instorage element 128. In some embodiments, the storage element 128comprises a storage device, such as the storage device 8905 describedabove in connection with FIGS. 90A and 90B.

In some embodiments, the mobile computing device 9005 does not have auser input I/O device 130 and/or a user output I/O device 130. In otherembodiments, the mobile computing device 9005 obtains or derives powerfrom the connection to the computing device 8910, such as for example,from a USB connection. In still other embodiments, the mobile computingdevice 9005 is a card of the following type: CompactFlash, Memory Stick,MultiMediaCard, Secure Digital, or SmartMedia.

In one embodiment, the storage element 128 stores a plurality ofcomputing environments and a plurality of virtual machine images. Inanother embodiment, the storage element 128 stores one or more of aplurality of virtual machine images providing one of a differentoperating system or a different application than at least one virtualmachine images accessible to the computing device. In still another ofthese embodiments, the storage element 128 stores one of the dataassociated with at least one computing environment and the at least onevirtual machine image in an encrypted format.

In some embodiments, the mobile computing device 9005 stores dataassociated with at least one portable computing environment 8920. In oneof these embodiments, the mobile computing device 9005 stores dataassociated with a plurality of portable computing environments 8920a-8920 n. In another of these embodiments, each of the portablecomputing environments 8920 a-8920 n comprises the same virtualizationsoftware 8921 a-8921 n. In still another of these embodiments, theportable computing environments 8920 a-8920 n comprise differentvirtualization software 8921 a-8921 n.

In other embodiments, the portable computing environments 8920 a-8920 nmay comprise at least one virtualization software 8921 a that is thesame as another virtualization software 8921 b. In other embodiments,the portable computing environments 8920 a-8920 n may comprise at leastone virtualization software 8921 a that is different from anothervirtualization software 8921 b. In yet another embodiment, there may beone copy of the virtualization software 8921 to be used for each of thevirtual images 8925 a-8925 n in storage 128.

In one embodiment, one or more of the virtual machine images 8925 a-8925n provides access to the same operating system or are used on the sameoperating system. In another embodiment, one or more of the virtualmachine images 8925 a-8925 n comprises a different operating system orexecutes on a different operating system. In some embodiments, thevirtual machine images 8925 a-8925 n share the same user data 8930. Inother embodiments, the virtual machine images 8925 a-8925 n may eachhave distinct sets of user data 8930 a-8930 n. In one embodiment, one ofthe virtual machine images 8925 a-8925 n may provide access to a firstcomputing environment, for example, a work desktop environment. Inanother embodiment, one of the virtual machine images 8925 a-8925 n mayprovide access to a second computing environment, for example, a homedesktop environment. In some embodiments, a virtual machine image 8925a-8925 n may provide access to a computing environment comprising a setof one or more portable applications of the user. The mobile computingdevice 9005 may store any desired set of one or more user environments8920 a-8920 n.

The mobile computing device 9005 includes a connector for connecting themobile computing device 9005 to a computing device, such as thecomputing device 8910. In one embodiment, the connector is connectableto a computing device 8910 via one of the following: a wirelessconnection, a USB connection, a Firewire connection, a Bluetoothconnection, a Wi-Fi connection, a network connection, and a dockingconnection.

The mobile computing device 9005 includes a loading mechanism 8940 forautomatically loading the at least one computing environment from thestorage element onto a computing device upon connection of the mobilecomputing device to the computing device via the connector. In oneembodiment, the loading mechanism 8940 automatically installs the atleast one computing environment on the computing device 8910. In anotherembodiment, the loading mechanism 8940 automatically executes the atleast one computing environment on the computing device 8910. In stillanother embodiment, the loading mechanism 8940 accesses at least onevirtual machine image stored in the storage element 128 to execute avirtual machine, the virtual machine providing access to a computingenvironment.

In some embodiments, the mobile computing device 9005 includes a userinterface provided for a user to select one virtual machine image toexecute on the computing device 8910 from a plurality of virtual machineimages. In other embodiments, the computing device 8910 provides theuser interface.

In one embodiment, a selection mechanism, such as a computingenvironment selector 9250 provides a user interface for a user to selectone of the portable computing environments 8920 a-8920 n to execute orestablish on the computing device 8910. The computing environmentselector 9250 may comprise software, hardware, or any combination ofsoftware and hardware. In some embodiments, the computing environmentselector 9250 has a graphical user interface providing a list of the oneor more portable computing environment 8920 a-8920 n stored in themobile computing device 9005. In other embodiments, the computingenvironment selector 9250 may comprise a command line interface. In oneembodiment, the computing environment selector 9250 comprises software,stored on or provided by either the mobile computing device 9005 or thecomputing device 8910. In one embodiment, the virtualized software 8921,virtualized layer 8922 or portable computing environment 8920 comprisesthe computing environment selector 9250. In another embodiment, thecomputing environment selector 9250 is executed on the mobile computingdevice 9005. In some embodiments, the computing environment selector9250 comprises a hardware and software mechanism on the mobile computingdevice 9005 for a user to select one of the portable computingenvironments 8920 a-8920 n. For example, the mobile computing device9005 may provide via a screen or visual display unit a text based userinterface with a thumb wheel to select a portable computing environment8920 a-8920 n.

Referring now to FIG. 92B, a flow diagram depicts another embodiment ofthe steps taken in a method for establishing a computing environment ona computing device via a mobile computing device. By connecting themobile computing device 9005 carrying a portable computing environment8920 a-8920 n to a computing device 8910, a user establishes avirtualized computing environment 8920′ on the computing device 8910. Inbrief overview, at step 9255, the mobile computing device 9005 isconnected to the computing device 8910, and at step 9260, the computingdevice 8910 detects the connection. At step 9265, and in someembodiments, the user selects a portable computing environment 8920a-8920 n from storage to be used on the computing device 8910. At step9270, a portable computing environment 8920 a-8920 n in the storageelement 128 is decrypted. At step 9275, the virtualization software 8921is automatically loaded on the computing device 8910. At step 9280, thecomputing device 8910 executes a virtual machine 8925′ in thevirtualized environment 8922 based on the portable computing environment8920 a-8920 n, such as by accessing virtual image 8925. At step 9285,the computing device 8910 controls access to the computing device 8910via the virtualized computing environment 8920′.

In further detail, at step 9255, the mobile computing device 9005 isconnected to the computing device 8910 by any suitable means and/ormechanisms. At step 9260, the computing device 8910 detects theconnection. In some embodiments, the operating system of the computingdevice 8910 detects connection of the mobile computing device 9005. Inother embodiments, a device manager detects the connection of the mobilecomputing device 9005. In still other embodiments, a plug-and-playmanager detects the connection of the mobile computing device 9005. Inother embodiments, a device driver for the computing device 8910 detectsthe connection. In yet another embodiment, the loading mechanism 8940′detects the connection of the mobile computing device 9005.

In some embodiments, upon detection of the connection, the computingdevice 8910 may automatically install, load, and execute a devicedriver, software, application, process, service, thread or task toperform any of the operations described herein, as described above inconnection with FIGS. 89A and 89B, FIGS. 90A and 90B, and FIGS. 91A and91B. In other embodiments, upon detection of the connection, computingdevice 8910 may perform any type and form of authentication andauthorization of the user of the mobile computing device 9005.

At step 9265, the user selects a portable computing environment 8920a-8920 n from storage element 128 to establish as the computingenvironment 8920′ on the computing device 8910. For example, the usermay identify or select, via the computing environment selector 9250, theportable computing environment 8920 a-8920 n to run on the computingdevice 8910. In one embodiment, the computing device 8910 displays auser interface providing a list of portable computing environments 8920a-8920 n from the mobile computing device 9005 for the user to select toestablish on the computing device 8910. In some embodiments, thecomputing device 8910 executes an application program identified via thestorage element 128 of the mobile computing device 9005, such as via anautorun file. In another embodiment, the mobile computing device 9005has a visual display unit displaying a user interface for the user toselect one of the portable computing environments 8920 a-8920 n. In someembodiments, one of the portable computing environments 8920 a-8920 n isidentified as a default computing environment 8920 to establish on thecomputing device 8910. In another embodiment, the portable computingenvironments 8920 a-8920 n are identified in an order or preference orpriority. In one embodiment, the mobile computing device 9005 comprisesone portable computing environment 8920. In this embodiment, theportable computing environment 8920 may not need to be selected by theuser and is automatically used by the computing device 8910. In anotherembodiment, although there is one portable computing environment 8920 onthe mobile computing device 9005, the user may select the one portablecomputing environment 8920.

At step 9270, the computing device 8910 may perform decryption on anyportion of storage element 128 which may be encrypted. In oneembodiment, the storage element 128 comprises an encrypted file system.In another embodiment, the virtualization software 8921, virtual image8925 and/or user data 8930, or any portions thereof may be encrypted. Inone embodiment, the computing device 8910, decrypts the portion ofstorage 128 using a key via the loading mechanism 8940′, thevirtualization layer 8920, or another set of executable instructions. Insome embodiments, the key may a public key. In other embodiments, thekey may be a private key. In one embodiment, the decryption key may beidentity-based, such as based on the identity of a user authenticatedvia the computing device 8910. In another embodiment, the user'sauthentication credentials, such as user ID and/or password, may be usedto generate or obtain a key for decryption. For example, the user'sauthentication credentials may be used to obtain a key stored in thedatabase. In another embodiment, the computing device 8910 generates aprivate key based on performing an algorithm on the user'sauthentication credentials and a public key, such as a public keyprovided by a trusted third party. In yet another embodiment, the mobilecomputing device 9005 may store a key that is used by the computingdevice 8910 to authenticate the user and/or generate a decryption key.In some embodiments, the computing device 8910 uses a ticket authorityto obtain a ticket for decrypting the encrypted portions of storage 128.Any type and form of authentication technologies may be used inperforming the operations described herein, such as password basedauthentication or biometric authentication. In one embodiment, a tokenis used to provide two-factor authentication, such as a tokenmanufactured by RSA Security Inc. of Bedford, Mass.

At step 9275, the computing device 8910 provides or establishes thevirtualization layer 8922 on the host computing device 8910 as describedabove in connection with FIGS. 89A-89B, FIGS. 90A-90B, and FIGS.91A-91B.

At step 9280, the computing device 8910 automatically loads, executes orotherwise establishes a virtual machine 8925 a-8925 n to provide accessto a portable computing environment 8920 a-8920 n on the virtualizedlayer 8922. In one embodiment, the computing device 8910 and/or loadingmechanism 8940 accesses the virtual machine image 8925 a-8925 n from thestorage element 128 and loads or executes the virtual machine image 8925a-8925 n as a virtual machine 8925′ in the established virtualizedenvironment 8922. In another embodiment, the computing device 8910loads, executes or establishes a virtual machine as described above inconnection with FIGS. 89A-89B, FIGS. 90A-90B, and FIGS. 91A-91B.

At step 9285, in some embodiments, the computing environment 8920′ orvirtual machine 8925 is established in a secured manner. In oneembodiment, the established computing environment 8920′ protects accessto user data 8930 or portions of the computing environment 8920 from theenvironment of the computing device 8910 external to the computingenvironment 8920′. In one embodiment, the virtualization software 8921and/or virtualization layer 8922 ensures that contents of the virtualmachine 8925′ remain secure while running on the computing device 8910.In some embodiments, the virtualization software 8921 and/orvirtualization layer 8922 ensures that no input or no output is madeavailable to the environment of the computing device 8910 in apersistent fashion. For example, in one embodiment, the virtualizationsoftware 8921 and/or virtualization layer 8922 may disable clipboardaccess between the host environment and the virtual machine 8925′. Inanother embodiment, the virtualization software 8921 and/orvirtualization layer 8922 disables access to a file system, or portionthereof, of the computing device 8910. In other embodiments, thevirtualization software 8921 and/or virtualization layer 8922 preventspaging by the virtual machine 8925′ to the page file of the computingdevice 8910. In one embodiment, the virtual machine 8925′ uses thestorage element 128 on the mobile computing device 9005 for file anddata operations. In some embodiments, the virtualization layer 8922 actsas firewall between the virtual machine 8925′ and the host environment.In yet another embodiment, the virtualization software 8921 and/orvirtualization layer 8922 may provide a configuration mechanism, such asa user interface, to select which actions may be performed and/or datashared between the computing device 8910 and the virtual machine 8925′.

Although this method is generally discussed as establishing a computingenvironment 8920′ from one of a plurality of portable computingenvironments 8920 a-8920 n, a plurality of computing environments 8920′,8920″ may be established on the computing device 8910. For example, afirst computing environment 8920′ may be established on the computingdevice 8910 using a first portable computing environment 8920 a from themobile computing device 9005, and a second computing environment 8920″may be established on the computing device 8910 using a second portablecomputing environment 8920 b from the mobile computing device 9005.

Referring now to FIGS. 93A-93D, block diagrams depict embodiments ofsystems and methods for a mobile computing device to one or morehardware resources. The hardware resource may provide access toresources, such as a processor or memory with greater power, size,capacity or performance as compared to corresponding resources of themobile computing device. FIG. 93A depicts an embodiment of a mobilecomputing device 9005 connecting to a docking station or device having aprocessor, memory and other computing resources for use by the mobilecomputing device. FIG. 93B depicts an embodiment of a mobile computingdevice connecting to a second hardware resource, via a dockingmechanism, to use a processor, memory and/or resources of the secondhardware resource. FIG. 93C depicts an embodiment of a docking stationproviding connectivity to a second hardware resource, such as acomputing device, to use a processor, memory and/or resources of thesecond hardware resource. FIG. 93D depicts one embodiment of the stepstaken in a method of providing to a mobile computing device one or morehardware resources, as described in the environments illustrated inFIGS. 93A-93C. In some embodiments, a portable computing environment maybe established on the hardware resource in accordance with any of thesystems and method described in conjunction with FIGS. 89A-89B, 90A-90B,91A-91C, 92A-92B. In other embodiments, the computing environment of themobile computing device is accessed using the processor, memory, and/orresources of the hardware resource.

Referring now to FIG. 93A, in brief overview, the depicted systemincludes a mobile computing device 9005 connected to a hardware resource9302. The mobile computing device 9005 has a central processing unit102. The hardware resource 9302 has a central processing unit 102′. Inone embodiment, the hardware resource 9302 includes a docking station9310 providing access to the hardware resource 9302. In anotherembodiment, the docking station 9310 includes a processor 102′ andmemory 122′. In still another embodiment, the mobile computing deviceprovides the functionality of a mobile computing device 9005 asdescribed above in connection with FIGS. 90A, 90B, 91A, 91B, 92A, and92B.

The mobile computing device 9005 comprises a connection mechanism 9305for connecting the mobile computing device 9005 to the hardware resource9302. The mobile computing device 9005 uses the central processing unit102 to effect an initial quanta of work and uses the central processingunit 102′ of the hardware resource 9302 to effect subsequent quanta ofwork when connected to the hardware resource 9302. In one embodiment,the mobile computing device 9005 uses the connection mechanism 9305 toswitch to using the processing or computing capabilities of the hardwareresource 9302 upon or after connecting to the hardware resource 9302.For example, the mobile computing device 9005 may execute a computingenvironment 8920 on the hardware resource 9302 after connecting to thedocking station 9310.

In one embodiment, the mobile computing device 9005 connects to thehardware resource 9302 via connection across network 150. In anotherembodiment, the mobile computing device 8905 is docked to the hardwareresource 9302 via a I/O device mechanism 130 a-130 n designed andconstructed to connect to, and/or interface or communicate with the typeand form of mobile computing device 9005. In one embodiment, the mobilecomputing device 9005 is docked to the hardware resource 9302 via adocking connector. For example, one of the devices 9005 or 9310 may havea docking connector, and one of the device 9005 or 9310 may have acorresponding interface or connection mechanism designed to receive theconnector.

The connection mechanism 9305 may comprise software, hardware, or anycombination of software and hardware enabling the mobile computingdevice 9005 to access the hardware resource 9302. In some embodiments,the connection mechanism 9305 comprises any type and form of integratedcircuit, such as a Field Programmable Gate Array (FPGA), ProgrammableLogic Device (PLD), or Application Specific Integrated Circuit (ASIC)capable of performing any of the operations described herein.

In one embodiment, the connection mechanism 9305 comprises one of thefollowing: a wireless connection, a USB connection, a Firewireconnection, a Bluetooth connection, a Wi-Fi connection, a networkconnection, and a docking connection.

In some embodiments, the connection mechanism 9305 is enables the systemor mother board of the mobile computing device 9005 to use a processor102′ and/or memory 122′ of the hardware resource 9302. In otherembodiments, the connection mechanism 9305 communicates with any systemor data bus of the mobile computing device 9005 to transmit and receivesignals directing the mobile computing device 9005 to use a resource ofthe hardware resource 9302, such as the processor 102′ and memory 122′of the docking station 9310. In some embodiments, the connectionmechanism 9305 may communicate with a system or data bus of the hardwareresource 9302 to enable the use of resources of the hardware resource9302 by the mobile computing device 9005.

In one embodiment, the connection mechanism 9305 may have the mobilecomputing device 9005 reboot, restart or reset when connected or dockedto the hardware resource 9302. In another embodiment, the connectionmechanism 9305 may allow real-time switching to use a computing resourceof the hardware resource 9302 without a reboot or restart. In someembodiments, the connection mechanism 9305 transfers data from memory122 on the mobile computing device 9005 to memory 122′ of hardwareresource 9302. In other embodiments, the connection mechanism 9305transfers execution of a process from a processor 102 on the mobilecomputing device 9005 to processor 102′ of the hardware resource 9302.In still other embodiments, the mobile computing device 9005 transferscentral processing control and management to the hardware resource 9302.In yet other embodiments, the connection mechanism 9305 provides for theuse of the processor 102 and/or memory 122 on the mobile computingdevice 9005 in conjunction with the processor 102′ and/or memory 122′ ofthe hardware resource 9302. For example, when connected to the hardwareresource 9302, the mobile computing device 9005 may operate as amulti-processor device.

In some embodiments, the mobile computing device 9005 and/or connectionmechanism 9305 maintains the state of the processor 102 and/or memory122 on the mobile computing device 9005. As such, in some of theseembodiments, upon disconnection from the hardware resource 9302, themobile computing environment 9005 continues from a state prior toconnection to the hardware resource 9302. In others of theseembodiments, the connection mechanism 9305 transfers data, information,and execution or control from a processor 102′ and/or memory 122′ to theprocessor 102 and/or memory 122 of the mobile computing device 9005.

In one embodiment, the connection mechanism 9305 comprises any type andform of user interface to receive user input regarding connection to thehardware resource 9302, use of hardware resources, and transfer of dataand control between hardware resources. For example, the connectionmechanism 9305 may display a graphical user interface upon docking tothe hardware resource 9302 for the user to setup, configure, controland/or manage the use of the hardware resource 9302.

In some embodiments, the hardware resource 9302 uses the storage element128 of the mobile computing device 9005 to provide access to a computingenvironment. In one of these embodiments, the hardware resource 9302executes an operating system stored in storage element 128 of theconnected mobile computing device 9005. In another of these embodiments,the hardware resource 9302 mounts the storage element 128 of theconnected mobile computing device 9005 for access by the hardwareresource 9302. In still another of these embodiments, the user uses theoperating system or computing environment of the hardware resource 9302but executes applications and accesses data on the storage element 128of the mobile computing device 9005. In yet another of theseembodiments, the mobile computing device 9005 may store portableapplications to execute in the hardware resource 9302.

In one embodiment, the hardware resource 9302 executes a virtual machineto provide access to a computing environment stored in the mobilecomputing device 9005. In another embodiment, the hardware resource 9302executes a virtual machine, the virtual machine providing access to avirtualized computing environment. In still another embodiment, a filefrom a storage location provided by the mobile computing device 9005 isaccessed by a user via the hardware resource 9302 when the mobilecomputing device 9005 is connected to the hardware resource 9302, andthe file is accessed by the user, via the mobile computing device 9005,when the mobile computing device 9005 is not connected to the hardwareresource 9302.

Still referring to FIG. 93A and in one embodiment, the hardware resource9302 comprises a docking station 9310, the docking station 9310comprising a computer system 100. In some embodiments, the dockingstation 9110 may be any type and form of computer system 100, asdescribed above in connection with FIGS. 1A-1B. In one of theseembodiments, and as described in connection with FIGS. 1A-1B, thedocking station 9110 may comprise components including, but not limitedto, a processor 102′, memory 122, storage 128, a network interface 118′,and/or one or more I/O devices 130 a-130 n. In another of theseembodiments, the docking station 9110 is connected to a display device124, a keyboard 126, and/or a pointing device 127. The docking station9310 may also be connected to or provide access to other hardwareresources and computing peripherals. In some embodiments, the dockingstation 9310 provides access to resources of another computer system 100via a network 150.

In one embodiment, the hardware resource 9302 has a processor 102′having a higher processor speed than the processor 102 of the mobilecomputing device 9005. In another embodiment, the hardware resource 9302has a processor 102′ comprising a processor architecture different thana processor architecture of the processor 102 of the mobile computingdevice 9005. In still another embodiment, the mobile computing device9005 uses the processor 102 to effect an initial quanta of work and,upon connection to the hardware resource 9302 via the connectionmechanism 9305, uses the processor 102′ to effect a subsequent quanta ofwork. In yet another embodiment, the mobile computing device 9005determines that a memory 122′ of the hardware resource 9302 has a memorysize larger than a memory size of a memory 122 of the mobile computingdevice 9005 and uses the memory 122′ of the hardware resource 9302 toeffect subsequent quanta of work.

In some embodiments, the mobile computing device 9005 uses a firstoperating system executing on the first central processing unit when notconnected to the hardware resource and a second operating systemexecuting on the second central processing unit when connected to thehardware resource. In one of these embodiments, the second operatingsystem is different than the first operating system.

Referring now to FIG. 93B, another embodiment of the hardware resource9302 and the mobile computing device 9005 is depicted. In briefoverview, the mobile computing device 9005 connects to a docking station9310 across a network 150, and in turn, docking station 9310 connects toa computing device 8910. In this embodiment, the hardware resource 9302includes a docking station 9310 connected to or in communication with acomputing device 8910. Instead of providing resources, such as aprocessor 102′ and memory 122′ as depicted in FIG. 93A, the dockingstation 9310 provides access to resources of a second computing device8910 via the connection across network 150′. In one embodiment, afterconnection to the docking station 9310, the mobile computing device 9005uses resources of the computing device 8910 via connections acrossnetworks 150 and 150′.

Referring now to FIG. 93C, another embodiment of the hardware resource9302 and the mobile computing device 9005 is depicted. In briefoverview, the mobile computing device 9005 connects to the computingdevice 8910 via docking mechanism 9310. In this embodiment, the hardwareresource 9302 includes a computing device 8910 having a docketingmechanism 9310, such as an I/O device or mechanism 130, to dock themobile computing device 9005. After connection via docking mechanism9310, the mobile computing device 9005 uses the resources of thecomputing device 8910, such as a processor and/or memory. In someembodiments, the hardware resource 9302 provides access the mobilecomputing device 9005 with access to a peripheral computing device.

In any of the embodiments depicted in FIGS. 93A-93C, the hardwareresource 9302 may provide resources and capabilities offering improvedpower, performance, or other operating or performance characteristicsdesired by the user of the mobile computing device 8905 or suitable forone or more applications of the mobile computing device, as described inmore detail above in connection with FIGS. 89A-89B, 90A-90B, 91A-91B,and 92A-92B.

Referring now to FIG. 93D, a flow diagram depicts one embodiment of thesteps taken in a method for providing to a mobile computing device oneor more hardware resources. In brief overview, the mobile computingdevice uses a first central processing unit of the mobile computingdevice 9005 to effect an initial quanta of work (step 9355). The mobilecomputing device 9005 connects to a hardware resource 9302 including asecond central processing unit (step 9360). The mobile computing deviceuses a second central processing unit of the hardware resource 9302 toeffect subsequent quanta of work (step 9365).

A mobile computing device uses a first central processing unit to effectan initial quanta of work (step 9355). In one embodiment, the mobilecomputing device is a computer 100 as described above in connection withFIG. 1A and 1B. In another embodiment, the mobile computing device is amobile computing device 9005 as described above in connection with FIGS.90A-92B.

The mobile computing device 9005 connects to a hardware resource 9302including a central processing unit (step 9360). In one embodiment, themobile computing device 9005 connects to the hardware resource 9302 byany suitable means and/or mechanisms. In some embodiments, the mobilecomputing device 8905 connects or docks to a docking station 9310providing one or more resources. In one of these embodiments, the mobilecomputing device 9005 connects to a docking station 9310 having aprocessor 102′ and/or memory 122′. In another of these embodiments, themobile computing device 9005 connects to a docking station 9310providing a connection to a second computing device 8910, the secondcomputing device 8910 including a processor 102′. In still another ofthese embodiments, the mobile computing device 9005 connects or docks toa docking mechanism 9310 of a host computing device 8910.

In some embodiments, the mobile computing device 8905 and the dockingstation 9110 may connect via any type and form of connection, wired,wireless or otherwise, including, but not limited to, via a wirelessconnection, a Wi-Fi connection, a USB connection, a Firewire connection,a Bluetooth connection, a network connection, and a docking connection.The mobile computing device 8905 and docking station 9110 maycommunicate via any type and form of protocol, such as a device, bus,communication, application, data, or network protocol.

The mobile computing device 9005 uses a central processing unit of thehardware resource 9302 (step 9370). In one embodiment, the mobilecomputing device 9005 initiates use of a processor 102′ and/or memory122′ of the hardware resource 9302 via a connection mechanism 9305. Inanother embodiment, the mobile computing device 9005 transfers executioncontrol and management to the central processing unit of the hardwareresource 9302. In still another embodiment, the mobile computing device9005 transfers data and information to the processor and/or memory ofthe hardware resource 9302. In some embodiments, the mobile computingdevice 9005 uses the processor and/or memory of the hardware resource9302 as a second processor and/or memory for the mobile computing device9005.

In one embodiment, the mobile computing device 9005 connects to ahardware resource 9302 comprising one of the following: a first dockingstation having the second central processing unit; a second computingdevice having the second central processing unit; and a second dockingstation providing access to a third computing device having the secondcentral processing unit.

In some embodiments, an application program on the mobile computingdevice 9005 executes in the processor 102′ and uses memory 122′ of thecomputing environment 9102 and displays on a visual display unit of themobile computing device 9005. In other embodiments, an applicationprogram executing on the processor and using the memory of the hardwareresource 9302 receives user input from an input device of the mobilecomputing device 9005. In still other embodiments, an applicationprogram executing on the processor and using the memory of the hardwareresource 9302 displays on a display device 124 of the hardware resource9302 while receiving input from an input mechanism of the mobilecomputing device 9005.

In one embodiment, an application program executing on the processor andusing the memory of the hardware resource 9302 displays on a visualdisplay unit of the mobile computing environment 9005 while receivinginput from an input device of the hardware resource 9302, such askeyboard 126 and pointing device 127. In some embodiments, the computingenvironment of mobile computing device 9005 executes on the processorand memory of the mobile computing device 9005 but also uses a resourceof the hardware resource 9302, such as a network connection, printer,display device, input device, or any I/O device 120.

In one embodiment, the mobile computing device 9005 determines that thesecond central processing unit has a processor speed greater than aprocessor speed of the first central processing unit and uses the secondcentral processing unit of the hardware resource to effect subsequentquanta of work. In another embodiment, the mobile computing device 9005determines that the second central processing unit has a processorarchitecture different than a processor architecture of the firstcentral processing unit and uses the second central processing unit ofthe hardware resource to effect subsequent quanta of work. In stillanother embodiment, the mobile computing device 9005 identifies a memoryof the mobile computing device 9005 and identifies a second memory ofthe hardware resource 9302. In yet another embodiment, the mobilecomputing device 9005 determines that the second memory of the hardwareresource has a memory size larger than a memory size of the first memoryof the mobile computing device and uses the second memory of thehardware resource to effect subsequent quanta of work.

In some embodiments, the hardware resource 9302 uses one or moreresources of the mobile computing device 9005. In one of theseembodiments, the hardware resource 9302 accesses a storage element orstorage device of the mobile computing device 9005, such as the storageelement 128. In some embodiments, the hardware resource 9302 mounts thestorage element 128. In another of these embodiments, the hardwareresource 9302 boots or reboots or otherwise establishes an environmentbased on a computing environment stored on the mounted storage element128. In still another of these embodiments, the hardware resource 9302uses the processor 102 and/or memory 122 of the mobile computing device9005 in addition to the processor and/or memory of the hardware resource9302.

In some embodiments, the hardware resource 9302 uses a display deviceand/or input device of the mobile computing device 9005. In otherembodiments, the hardware resource 9302 executes a computing environment8920′ based on a portable computing environment 8920 in the storageelement 128 of the mobile computing device 9005. In some embodiments,the portable computing environment 8920 may execute in the hardwareresource 9302 but display on and receive input from the mobile computingdevice 9005.

In one embodiment, the hardware resource 9302 provides the mobilecomputing device 9005 with access to a peripheral computing device ofthe hardware resource. In another embodiment, the mobile computingdevice 9005 uses a first operating system executing on the first centralprocessing unit on the mobile computing device 9005 when not connectedto the hardware resource 9302 and a second operating system executing onthe second central processing unit of the hardware resource 9302 whenconnected to the hardware resource 9302. In still another embodiment,the first operating system is different than the second operatingsystem. In yet another embodiment, a virtual machine executing on thehardware resource 9302 provides the mobile device 9005 with access to afirst operating system. In some embodiments, the hardware resource 9302executes a virtual machine to provide access to a computing environmentstored in the mobile computing device 9005. In other embodiments, themobile computing device 9005 provides access to a computing environmenton the hardware resource 9302. In still other embodiments, a useraccesses, via the hardware resource 9302, a file stored in the mobilecomputing device 9005 when the mobile computing device 9005 is connectedto the hardware resource 9302 and accessing, by the user, via the mobilecomputing device 9005, the file stored in the mobile computing device9005 when the mobile computing device 9005 is not connected to thehardware resource 9302.

In one embodiment, the mobile computing device 9005 uses a processor ofthe hardware resource 9302 to provide access to a computing environmentstored on the mobile computing device 9005. In another embodiment, themobile computing device 9005 uses a processor of the hardware resource9302 to provide access to an operating system stored on the mobilecomputing device 9005. In still another embodiment, the mobile computingdevice 9005 uses a processor of the hardware resource 9302 to provideaccess to an application program stored on the mobile computing device9005. In yet another embodiment, the mobile computing device 9005 uses aprocessor of the hardware resource 9302 to execute a virtual machine onthe hardware resource, responsive to a virtual machine image stored onthe mobile computing device. In some embodiments, the mobile computingdevice uses a processor of the hardware resource 9302 to provide accessto a computing environment stored on the hardware resource.

Referring now to FIG. 94A, a block diagram depicts one embodiment of amobile computing device having a plurality of processors. In briefoverview, mobile computing device 9005 comprises a first processor 102and a second processor 102′. The processors 102, 102′ may access amemory 122 and/or storage element 128 on the mobile computing device9005. The mobile computing device 9005 includes a switching mechanism9405 for switching between using the first processor 102 and the secondprocessor 102′. In some cases, the mobile computing device 9005 may havea lower-powered processor 102 for minimal functionality or standbyoperations, and have a higher-powered processor 102 for normaloperations or for applications suitable or requiring more powerfulprocessor capability. While mobile, the user may want to access featuressuch as email, calendar, and contact information much like a PDA orsmartphone. When accessing such applications, the mobile computingdevice 9005 may use the lower-powered processor 102 to lengthenbattery-life and conserve power. The user may at any time want to accessan application having higher processor requirements or suitability. Whenaccessing these applications, the mobile computing device 9005 may usethe higher-powered processor 102′.

In further detail, the processor 102 and processor 102′ may be the sametype and speed of processor. In other embodiments, the processor 102 andprocessor 102′ may be a different type and speed of processor. In someembodiments, processor 102 comprises a processing speed and/orcapability greater than processor 102′. In other embodiments, processor102′ comprises a processing speed and/or capability greater than theprocessor 102. In some embodiments, the processor 102 and 102′ aresingle core processors. In other embodiments, the processor 102 and 102′are multiple core processors. In one embodiment, the processor 102 is asingle core processor and processor 102′ is a multiple core processor,such as dual or quad core processor. In yet another embodiment, theprocessors 102 and 102′ comprise the same processor architecture and/orare manufactured by the same processor manufacturer. In otherembodiments, the processors 102 and 102′ comprise different processorarchitectures and/or are manufactured by different processormanufacturers.

In some embodiments, a first processor 102 comprises operationalcharacteristics designed and constructed for lower power consumption,longer battery life, performance and/or applications of a mobile orportable computing device. In one of these embodiments, a firstprocessor 102 may be referred to as a low-powered CPU. In otherembodiments, a second processor 102′ comprises operationalcharacteristics designed and constructed for the power, performanceand/or application requirements of a desktop computing environment,server computing environment, or otherwise a non-mobile computingenvironment. In one of these embodiments, the second processor 102′ maybe referred to as a high-powered CPU. In other embodiments, theprocessor 102 provides a first level of processing or processorcapability, and the second processor 102′ provides a second level ofprocessing or processor capability. In one of these embodiments, thesecond level of capability is greater or higher than the first level. Inanother of these embodiments, the second level of capability ispreferred over the first level. In still other embodiments, the mobilecomputing device uses the first processor for one or more applicationssuitable for the first level of power consumption and processingcapability, and the mobile computing device uses the second processorfor one or more applications suitable for the second level of powerconsumption and processing capability.

The switching mechanism 9405 enables the mobile computing device 9005 toswitch between using a first processor 102 and a second processor 102′,or any plurality of processors. In some embodiments, the switchingmechanism 9405 comprises any type and form of integrated circuit, suchas a Field Programmable Gate Array (FPGA), Programmable Logic Device(PLD), or Application Specific Integrated Circuit (ASIC) capable ofperforming any of the operations described herein. In some embodiments,the switching mechanism 9405 enables the system or mother board of themobile computing device 9005 to use a first processor 102. In someembodiments, the switching mechanism 9405 enables the system or motherboard of the mobile computing device 8905 to use a second processor102′. In one embodiment, the switching mechanism 9405 communicates withany system or data bus of the mobile computing device 9005 to transmitand/or receive signals directing the mobile computing device 9005 to usea second processor 102′ instead of a first processor 102, and likewiseto use the first processor 102 instead of the second processor 102′. Insome embodiments, the switching mechanism 9405 may interface and/orcommunicate with a system or data bus of the mobile computing device9005 to transmit and/or receive signals to use both the first processor102 and second processor 102′ instead of just the first processor 102 orthe second processor 102′.

In another embodiment, the switching mechanism 9405 transfers data andexecution from processor 102 to processor 102′ of the mobile computingdevice 9005. In some embodiments, the switching mechanism 9405 transferscentral processing control and management from a first processor 102 toa second processor 102′, or from the second processor 102′ to the firstprocessor 102. In one embodiment, the switching mechanism 9405 may havethe mobile computing device 9005 reboot, restart or reset when switchingbetween using a processor 102, 102′. In another embodiment, theswitching mechanism 9405 may perform real-time switching from processorto processor.

In some embodiments, the switching mechanism 9405 identifies acondition, event or trigger upon which to switch between using oneprocessor and another processor. In other embodiments, switchingmechanism switches to one of the first processor or the second processorbased on a user selection. In one of these embodiments, the switchingmechanism 9405 comprises a user interface, such as a graphical userinterface or a command line user interface, for a user to identify,specify or configure the conditions, events or triggers for performingswitching between processors. For example, the switching mechanism 9405may switch, automatically, manually or otherwise, between a firstprocessor 102 and a second processor 102′ based on any operationalcharacteristics of the mobile computing device 9005 or the processors102, 102′. In still other embodiments, the switch mechanism 9105switches between use of a processor based on a level of load of thefirst processor or second processor. In yet other embodiments, theswitch mechanism 9405 switches between use of a processor based on alevel of activity, such as task, processes, applications, of the firstprocessor 102 or second processor 102′. In some embodiments, the switchmechanism 9405 switches between using a first processor and a secondprocessor based on a level of consumption of power and/or battery life.In still another embodiment, the switch mechanism 9405 switches betweenuse of a processor based on a type of application actuated or executedon the mobile computing device 9005.

In another embodiment, the switching mechanism 9405 comprises a userinterface for the user to switch between processors 102, 102′. Forexample, using a hot key, set of key strokes, or selecting an icon in atask bar, a user may instruct, command or direct the mobile computingdevice 9005 and/or switching mechanism 9405 to switch betweenprocessors, use one processor instead of another, or use the pluralityof processors 102, 102′ at the same time.

Referring now to FIG. 94B, a flow diagram depicts one embodiment of amethod for switching, by a mobile computing device, between use ofmultiple processors. In brief overview, the mobile computing device usesa first processor designed and constructed to provide a first level ofpower consumption and processing capability (step 9455). The switchingmechanism determines to switch the mobile computing device to using asecond processor based on an operating characteristic of the mobilecomputing device, the second processor designed and constructed toprovide a second level of power consumption and processing capability(step 9460). The mobile computing device 9005 uses the second processorresponsive to the determination by the switching mechanism.

In further detail, the mobile computing device 9005 uses the firstprocessor (step 9455). In one embodiment, the switching mechanism 9405identifies the first processor 120 as the default processor for use bythe mobile computing device 9005. In another embodiment, the mobilecomputing device 9005 uses the first processor 120 upon starting,restarting or booting of the operating system on the mobile computingdevice 9005. In some embodiments, a user selects the first processor 120as the default processor. In one of these embodiments, the use may haveidentified the first processor 120 to the switching mechanism 9405.

The switching mechanism 9405 determines to switch the mobile computingdevice 9005 to using the second processor 120′, based on an operatingcharacteristic of the mobile computing device, the second processordesigned and constructed to provide a second level of power consumptionand processing capability (step 9460). In some embodiments, theswitching mechanism 9405 determines to switch based on operatingconditions or characteristics of the mobile computing device 9005, suchas the operating system, resource usage, memory usage, powerconsumption, load, and numbers of processes, applications, services ortasks.

In one embodiment, the second level of power consumption and processingcapability of the second processor comprises a level greater than thefirst level of power consumption and processing capability of the firstprocessor. In another embodiment, the mobile computing device uses thefirst processor for one or more applications suitable for the firstlevel of power consumption and processing capability, and uses thesecond processor for one or more applications suitable for the secondlevel of power consumption and processing capability. In still anotherembodiment, the switching mechanism 9405 switches to one of the firstprocessor or the second processor automatically based on the initiationof execution of an application.

In some embodiments, the switching mechanism 9405 switches to one of thefirst processor or the second processor automatically based on one ormore of the following operating characteristics: a level of load of oneof the first processor or the second processor, a level of activity ofone of the first processor or the second processor, and a level of powerconsumption of one of the first processor or the second processor. Inone of these embodiments, the switching mechanism 9405 determines theload, activity or power consumption of the first processor 102 is near,equal or greater than the processing capability of the first processor102. In another pf these embodiments, the switching mechanism 9405determines the processor requirements of an application executed by theuser or requested by the user for execution is near, equal or greaterthan the processing capability of the first processor 102.

In other embodiments, the switching mechanism 9405 determines the mobilecomputing device 9005 would perform at a more suitable performance oroperational level, or in a manner desired by the user if the mobilecomputing device 9005 was using the second level of processingcapability of the second processor 120′. In still other embodiments, auser selects to switch to using the second processor 120′. In one ofthese embodiments, a user, via a user interface, directs or instructsthe switching mechanism 9405 to switch the mobile computing device 9005to use the second processor 120′.

The mobile computing device 9005 uses the second processor 120 (step9465). In one embodiment, the mobile computing device 9005 uses thesecond processor 120′ instead of the first processor 120. In anotherembodiment, the mobile computing device 9005 uses the second processor120′ in addition to the first processor 120. In some embodiments, themobile computing device 9005 and/or switching mechanism 9405 transfersinformation, data, control and/or management to the second processor120′ to continue operation of the operating system, applications,process, services or tasks executing on the first processor 102. Inother embodiments, new applications or processes initiated by the userare executed on the second processor 120′.

In some embodiments, the switching mechanism 9405 switches to having themobile computing device 9005 use the first processor 120 for a firstlevel of processing capability. As with step 9460, the switchingmechanism 9405 determines to switch based on the operating conditions orcharacteristics of the device 9005, such as the operating system,resource usage, memory usage, power consumption, load, and numbers ofprocesses, applications, services or tasks. For example, in oneembodiment, the switching mechanism 9405 determines the load, activityor power consumption of the second processor 102′ is greater than theprocessing capability needed for operating the mobile computing device9005 in its current state. In another embodiment, the switchingmechanism 9405 determines the processor requirements of an applicationexecuted by the user or requested by the user for execution is near, orequal to the processing capability of the first processor 102. In someembodiments, the switching mechanism 9405 determines the processorrequirements of an application executed by the user or requested by theuser for execution is less than the second level of processingcapability of processor 120′. In other embodiments, the switchingmechanism 9405 determines the mobile computing device 9005 would performat a suitable performance or operational level, or in a manner desiredby the user if the mobile computing device 9005 was using the firstlevel of processing capability of the first processor 120. For example,the mobile computing device 9005 would perform in a suitable manner forthe user using the first processor 102 but would also save on batterylife or reduce power consumption. In yet another embodiment, a userselects to switch to using the first processor 120. For example, in oneembodiment, the user via a user interface directs or instructs theswitching mechanism 9405 to switch the mobile computing device 9005 touse the first processor 120. The method 9450 may be performed again toswitch the mobile computing device 9005 to using the first processor atstep 9455.

Referring still to FIG. 8, in some embodiments, the session managementcomponent 1300 uses a connection to transmit information associated witha monitor on the client machine 10 to the virtual machine servicecomponent. In one of these embodiments, multi-monitor geometry supportis provided. In another of these embodiments, the session managementcomponent 1300 accesses multi-monitor information and enables thevirtual machine service component to create a version of themulti-monitor information in the virtual machine.

In one embodiment, techniques are provided for virtualizing a displayenvironment of a client by modifying and controlling the behavior andappearance of an application's window based on a desired display layoutfor the client. The techniques may be used for simulating or providing amultiple display setup for a single display environment. One embodimentprovides a window processing mechanism to intercept a selected messageto a window of an application and modify the message to the window todisplay the window on the client based on the desired display layout.The message to the window provides for the behavior or appearance of awindow used or displayed by the application. In one embodiment, thewindow processing mechanism provides a hooking mechanism to anapplication's window procedure and replaces the original windowprocedure with a window procedure designed to intercept a selectedwindow message and modify values of arguments or parameters of theintercepted window message based on the desired display layout of theclient. As such, selected window messages are processed to provide ortranslate the behavior or appearance of the window to the desireddisplay layout.

The techniques and mechanisms described may be practiced in aserver-based computing environment, such as between a client machine 10and a remote machine 30 communicating via a remote display protocol. Aremote machine 30, or a virtual machine executing in a hypervisor on theremote machine 30, may be setup or configured for a single displayenvironment while the client machine 10 may be setup or configured forone or more display devices. For example, a session on a machine, suchas a session on a WINDOWS server operating system may only be able to beconfigured or setup for a single display. The server may obtain apreferred or desired display layout for the client, and store thedisplay layout in association with the client, such as associating thedisplay layout with a remote session for the client. The window messageprocessing mechanism may be used by the server to intercept and modifyselected messages to windows of the application running on the server onbehalf of the client. The window messages are modified to provide abehavior or appearance of the window based on the display layoutassociated with the client. As such, the display output communicated bythe server to the client includes display output to be displayed on theclient according to the client's display layout rather than the displaylayout, e.g., single display layout, of the session on the server.

Using the techniques and mechanisms described herein allows a user toaccess a remotely available application in a server-based computingenvironment regardless of the monitor layout of the client. Instead ofthe server associating a single display with the remote session, theserver will provide display output based on the client's display layout.Furthermore, remotely-provided application may maximize to the properdisplay from the perspective of the client. Also, menu items and otherwindows of an application may be displayed appropriately within anapplication, for example, without appearing disjoint from theapplication. Additionally, the issue of a window being renderedoff-screen after changes to the display layout is handled byautomatically moving the window to a viewable upon detection of anoff-screen window.

Furthermore, these techniques and mechanisms may also be practiced in alocal computing environment to virtualize, simulate, or otherwiseprovide a multiple monitor environment for a client having a singledisplay device. Although the client may have a single display device, adesired display layout may be configured or provided to specify multipledisplays. The window processing mechanism may be used to intercept andmodify window messages for an application on the client to control thebehavior or appearance of the window based on the desired display layoutinstead of the actual monitor layout. As such, a user may gain thefunctionality, benefits, and advantages of a multiple monitorenvironment without having multiple display devices.

Referring now to FIG. 15A, one embodiment of an environment 1502 isdepicted. In brief overview, a client machine 10, may be connected to orotherwise use a display device 124, in one embodiment, or multipledisplay devices 124 a-124 n, in another embodiment. The client machine10 includes a display layout 1520 comprising a desired displayconfiguration for the client machine 10, such as for display device 124.The client machine 10 includes a storage element 1525 for storing thedisplay layout of the client machine 10. The client machine 10 alsoincludes a window processing mechanism 1550.

In further detail, the display layout 1520 comprises any type and/orform of information or data to identify, specify, or describe a desireddisplay layout configuration for the client. In one embodiment, thedisplay layout 1520 may comprise a file or set of files in any format.In another embodiment, the display layout 1520 may comprise anyinformation or data stored in any type and/or form of storage or memoryelement provided by the client machine 10. In an additional embodiment,the display layout 1520 may be provided or stored in any suitable typeand/or form of database. In further embodiments, the display layout 1520may be provided via any object, data structure, or applicationprogramming interface (API). The display layout 1520 may comprise anygraphical, textual, or combination of graphical and textual elements.The display layout 1520 may be created, edited, configured, or otherwiseprovided by any suitable means and/or mechanisms, such as a graphicaland/or text-based tool, program or application. In one embodiment, agraphical tool with a user interface may be used to design, create, editand configure the display layout 1520.

The display layout 1520 may include attributes, properties,characteristics, values, settings, profiles, and other displayconfiguration information 1522 a-1522 n to define each display for theclient. The display layout 1520 may include display configuration 1522a-1522 n for each of the desired displays, physical, virtual, orotherwise. In some embodiments, the display layout 1520 includes adescription of the layout, location, position, organization, orarrangement for each display device 124 a-124 n. In one embodiment, thedisplay layout 1520 includes a visual or graphical arrangementidentifying the location and/or size of each monitor with respect toeach other. In some embodiments, each display 1522 a-1522 n isidentified by an identifier, such as a name or number. Also, the displayconfiguration 1522 a-1522 n may include a monitor type, a screen refreshrate, adapter type, adapter information, screen resolution, a colorquality, a color scheme, a font size, a background, a style for buttonsand menus, and a screen saver.

Additionally, the display configuration 1522 a-1522 n may includeinformation or data to identify or specify a resolution 1524 a-1524 nand/or a work area 1526 a-1526 n for each display, such as the displaycorresponding to a display device 124 a-124 n. In one embodiment, theresolution 1524 a-1524 n identifies the number of pixels, or individualpoints of color, contained on a display monitor, expressed in terms ofthe number of pixels on the horizontal axis and the number of pixels onthe vertical axis. As those ordinarily skilled in the art willappreciate, the sharpness of the image displayed on the display device124 a-124 n may depend on the resolution and the size of the displaydevice 124 a-124 n. Inanother embodiment, the work area 1526 a-1526 nidentifies the usable dimensions of the screen area of the displaydevice 124 a-124 n in pixels. In some embodiments, the work area 1526a-1526 n does not include the dimensions of the screen area not useableby the user, such as the portion of the screen area having a menu, tool,or task bar, such as the task bar on a desktop provided via a WINDOWSoperating system.

In one embodiment, the display layout 1520 is configured to correspondto the number of display devices 124 a-124 n, and their availablefeatures and characteristics, accessible by the client. In otherembodiments, the display layout 1520 does not match or correspond to thenumber of display devices 124 a-124 n connected to the client. Forexample, the client machine 10 may have a single display device 124 abut the display layout 1520 may be configured for multiple displaydevices 124 a-124 n. In one aspect, the display layout 1520 may beconfigured for a display device 124 a that is virtual, or a virtualdisplay device. A virtual display device is rendered off the screen areaof the physical display device 124 a and may be placed on and off thevisible screen area by any suitable mechanism and/or means, such as forexample, tabbing between desktops, or panning and scrolling beyond thework area of the physical display device 124 a. A virtual display devicemay comprise a resolution 1524 a-1524 n, a work area 1526 a-1526 n, andany other data or information in a display configuration 1522 a-1522 nas if it was a physical display device 1524 a-1524 n connected or to beconnected to a client machine 10.

In some embodiments, the work area 1526 a-1526 n of the virtual displaydevice is relative to and/or adjacent horizontally or vertically to thescreen area of the physical display device 124 a-124 n. In otherembodiments, the resolution 1524 a-1524 n of the virtual display deviceis the same resolution 1524 a-1524 n of the physical display device 124a, or one of the resolutions 1524 a-1524 n supported by the physicaldisplay device 124 a. In some embodiments, a display 1522 acorresponding to a physical display device 124 a is not required to beconfigured as the top left monitor. In other embodiments, the displaylayout 1520 may comprise any arrangement of positive and/or negativecoordinate systems, and any displays 1522 a-1522 n, or display devices124 a-124 n, virtual or otherwise, may be configured to be located withany positive and/or negative coordinates, or in any portion of thepositive and/or negative coordinate system.

The storage element 1525 illustrated in the client machine 10 of FIG.15A may comprise any type and/or form of storage or memory, such asrandom-access memory, a disk drive, a disk array, a rewriteable opticaldrive, shared memory, a database, a file, an object, a data structure,or any other type and/or form of storage or memory element that allowsthe storing of and access to information or data, such as the displaylayout 1520. Inone embodiment, storage element 1525 provides the displaylayout 1520 as a globally mapped data file, which may be accessible byany of the applications 1530 of the client machine 10. In someembodiments, the storage element 1525 stores the display layout 1520, ora portion of the display layout 1520. In other embodiments, the displaylayout 1520 may be converted, translated, transformed or otherwisealtered to be stored in the storage element 1525. Although the storageelement 1525 is illustrated on the client machine 10, another clientmachine 10 accessible to the client machine 10, such as a server, mayhave a storage element for storing the display layout 1520.

In some embodiments, the client machine 10 executes or otherwiseprovides one or more applications 1530. The application 1530 can be anytype and/or form of software, program, or executable instructions suchas any type and/or form of web browser, web-based client, client-serverapplication, a thin-client computing client, an ActiveX control, or aJava applet, or any other type and/or form of executable instructionscapable of executing on client machine 10. In some embodiments, theapplication 1530 provides one or more windows 1535 a-1535 n, alsosometimes collectively referenced herein as 1535. Inone embodiment, thewindow 1535 a-1535 n is a graphic, sometimes rectangular in shape,having either some kind of user interface or graphical or textualrepresentation of the output of, and in some cases, allowing input forthe application 1530. Inanother embodiment, the window 1535 a-1535 ncomprises an area on the screen that displays information, includinguser documents as well as communications such as alert boxes and dialogboxes. Additionally, the user may open or close a window, move it aroundon the display, and sometimes change its size, scroll through it, andedit its contents.

In one embodiment, the user interface for the application 1530 is thewindow 1535 a-1535 n. In other embodiments, the application 1530provides a top level window 1535 a-1535 n for the presentation and/ornavigation structure or framework for the application 1530, and providesadditional windows 1535 a-1535 n in response to input or other events.For example, the application 1530 may have a menu system and screen areafor a user interface represented by a top level window 1535 a, and basedon user input, displays a secondary or smaller window 1535 to provideoutput to the user and/or receive input from the user regarding theapplication 1530.

The application 1530, and/or any windows 1535 a-1535 n of theapplication may receive a message 1540, such as a window message, asinput. The message 1540 may be any type and/or form of communication viaany type and/or form of medium. In some embodiments, the message 1540comprises a communication to a window 1535 a-1535 n to control or directthe behavior, appearance, attributes, or properties of the window 1535a-1535 n. In an exemplary embodiment of a WINDOWS-based environment, theapplication 1530 is event-driven, and waits for the operating system, orsystem, to pass input to them. The system passes all input foranapplication to the various windows 1535 a-1535 n in the application1530. Each window 1535 a-1535 n has a function, called a windowprocedure, which the operating system calls in response to receivinginput for the window. A window procedure is a function that receives andprocesses all messages sent to the window. A window class may have awindow procedure, and every window created with that class uses thatsame window procedure to respond to messages. The window procedureprocesses the input and returns control to the system. The system passesinput to a window procedure in the form of a message 1540, which may begenerated by the operating system or other applications 1530. A message1540 may be generated for an input event, for example, when the usertypes, moves the mouse, or clicks a control such as a scroll bar. Amessage 1540 may also be generated in response to changes in theoperating system or computing device brought about by an application1530. An application 1530 can generate messages to direct windows 1535a-1535 n of the application 1530 to perform tasks or to communicate withwindows 1535 a-1535 n in other applications.

In the exemplary embodiment of a WINDOWS-based system, a message 1540 issent to a window procedure with parameters. Inone embodiment, themessage 1540 comprises a set of four parameters: a window handle, amessage identifier, and two values referred to as message parameters.The window handle identifies the window for which the message isintended, and is used to determine which window procedure should receivethe message. A message identifier identifies a purpose or function ofthe message 1540. When a window procedure receives a message, it usesthe message identifier to determine how to process the message. Forexample, a message identifier WM_PAINT of a message 1540 may indicate toa window procedure that the window's 1535 client area has changed andmust be repainted. The parameters of a message 1540 may specify data orthe location of data used by a window procedure when processing amessage 1540. The meaning and value of the parameters may depend on themessage 1540. A message parameter can include an integer, a string,packed bit flags, a pointer to a structure containing additional data,or any type and/or form of data or information.

Although a message 1540 is generally described in the context of aWINDOWS-based environment, a message 1540 may be any type and/or form ofcommunication in any type of operating system or environment, as oneordinarily skilled in the art would recognize and appreciate, to controlor direct the appearance, behavior and attributes of a window 1540 beingdisplayed or otherwise being used, processed, or provided by theapplication 1530. As such, the message 1540 may be in a form and havecontent suitable to the environment or operating system for which theoperations described herein may be practiced.

Still referring to FIG. 15A, the window processing mechanism 1550, alsoreferred to as a window message processing mechanism, provides the meansand mechanism for changing, controlling or directing an appearance,behavior or attribute of the window 1535 a-1535 n of an application 1530based on the desired display layout 1520 of the client 1505. The windowprocessing mechanism 1550 may comprise an application programminginterface (API), application, module, software component, library,service, process, task or any other form and/or type of executableinstructions designed to and capable of executing or providing thefunctionality described herein. The window processing mechanism 1550 maycomprise software, hardware, or any combination of software andhardware. In some embodiments, an application 1530 may be designed orconstructed to include the functionality of the window processingmechanism 1550, while in some other embodiments, the window processingmechanism 1550 is designed and constructed to be used by existingapplications 1530, for example, without changing the application 1530.

In one embodiment, the window processing mechanism 1550 comprises amechanism for subclassing window procedures of a window 1535 of theapplication 1530, and providing a window procedure that gets called orused in place of the original window procedure of the window 1535.

In one embodiment, a hooking mechanism is used by the window processingmechanism 1550 to provide the replacement window procedure. In someembodiments, a hooking mechanism comprises using an applicationprogramming interface (API) to replace the executable instructions orcode of a function, procedure, or API with a desired set of executableinstructions or code. For example, the window processing mechanism 1550may introduce a hooking mechanism for any API related to creating,establishing, or providing a window 1535, for example, theCreateWindowA, CreateWindowW, CreateWindowExA, and CreateWindowExW APIsof the WINDOWS operating system environment. In some embodiments, thewindow procedure is replaced via the Windows application programminginterface (API) calls of GetWindowLong and SetWindowLong. In otherembodiments, the replaced window procedure is stored in a list of anysuitable type and/or form along with a window handle or reference to thereplaced window procedure. As such, the window procedure used by thewindow processing mechanism 1550 may call the replaced window procedure.For example, the window processing mechanism 1550 may pass through amessage 1540 to the original window procedure for processing.

The window procedure of the window processing mechanism 1550 may beconstructed and designed to intercept all or a portion of the messages1540 communicated to or received by the window 1535. In someembodiments, the window procedure intercepts all messages 1540 and anymessages 1540 not to be modified are communicated to the original orreplaced window procedure. In one embodiment of a Microsoft® Windowsbased environment, the window procedure of the window processingmechanism 1550 intercepts messages 1540 with a message identifiercomprising one of the following: 1) WM_DISPLAYCHANGE, 2) WM₁₃WINDOWPOSCHANGED, 3) WM₁₃ WINDOWPOSCHANGING, and 4) WM_GETMAXMININFO. AWM₁₃ DISPLAYCHANGE message 1540 communicates to a window 1535 a changein a resolution 1524 of a display 124. A WM₁₃ WINDOWPOSCHANGED message1540 communicates to a window 1535 a change in a size, position, or aplace in the Z order for the window 1540. A WM₁₃ WINDOWPOSCHANGINGmessage 1540 is communicate to a window 1535 when a change in a size,position, or a place in the Z order for the window 1540 is about tooccur. A WM₁₃ GETMAXMININFO message 1540 is communicated to a window1535 when a size or position, or a window 1540 is about to change.

The window processing mechanism 1550 intercepts a message 1540 andmodifies a return value or parameter of the message 1540 to correspondto or be based on the display layout 1520. In some embodiments, thewindow processing mechanism 1550 intercepts messages 1540 for atop-level window 1535, and in other embodiments, the window processingmechanism 1550 intercepts messages for windows 1535 that are not atop-level window. In further embodiments, the window processingmechanism 1550 intercepts messages 1540 for a certain set of windows1540. For example, the window processing mechanism 1550 may beconfigured to intercept windows 1550 defined in a list, database,storage 1525, or any other type and/or form of configuration medium.

The message 1540 intercepted by the window processing mechanism 1550 mayhave return values, arguments, and/or parameters designed or targetedfor the actual display layout of the client machine 10 or remote machine30, but the window processing mechanism 1550 changes the return values,arguments and/or parameters to be designed or targeted for the displayconfiguration 1522 a-1522 n provided by the desired display layout 1520.The window processing mechanism 1550 may read, access, acquire orotherwise obtain the display layout 1520 from the storage element 1525by any suitable means and/or mechanism. The window processing mechanism1550 may comprise any type of logic, functionality, business rules, oroperations to obtain the values, arguments, and parameters of themessage 1540 and analyze, compare or otherwise process the values,arguments, and parameters of the message 1540 in view of the displaylayout 1520, and determine any changes or modifications to the values,arguments or parameters or the message 1540 to display the window 1535on a display identified by the display layout 1520. The windowprocessing mechanism 1550 modifies the message 1540 according to thedetermined changes and communicates the message 1540 to the window 1535.In some embodiments, the window processing mechanism 1550 determines themessage 1540 does not need to be modified and thus communicates themessage 1540 in the same form as intercepted by the window processingmechanism 1550. In other embodiments, the window processing mechanism1550 replaces the message 1540 with a second message.

Referring now to FIG. 15B, another embodiment of a networked computerenvironment is shown in which the client machine 10 communicates with aremote machine 30 via one or more communication networks 150. The clientmachine 10 may be connected to or otherwise use one or more displaydevices 124 a-124 n. The client machine 10 includes a display layout1520 comprising a desired display configuration for the client machine10, such as for display devices 124 a-124 n. The client machine 10 mayalso include a client agent 1508. The remote machine 30 includes anapplication 1530 providing one or more windows 1535 a-1535 n, and astorage element 1525 for storing the display layout 1520 of the clientmachine 10. The remote machine 30 also includes a server agent 1528, asession login mechanism 1545, and a window processing mechanism 1550.

The environment 1500 may provide a server-based or thin-client computingenvironment for practicing the operations described herein. For example,the application 1530 may be an application executed on the remotemachine 30 on behalf of the client machine 10. The display output fromexecution of the application 1530 may be communicated to the clientmachine 10 for display on the client, for example, via the client agent1508. The display output may be communicated between the remote machine30 and client machine 10 via a remote display protocol. The displayoutput may be based on a window 1540 of the application 1530 running onthe remote machine 30 but to be displayed on the client machine 10. Aswill be described in further detail below, the window processingmechanism 1550 on the remote machine 30 intercepts and modifies messages1540 of the application 1530 running on the remote machine 30,communicates the message 1540 to the window 1535. As such, the displayoutput communicated to the client machine 10 reflects the modifiedmessage 1540 processed by the window 1535.

In one embodiment, as shown in FIG. 15B, a client agent 1508 is includedwithin the client machine 10. The client agent 1508 can be, for example,implemented as a software program and/or as a hardware device, such as,for example, an ASIC or an FPGA. An example of a client agent 1508 witha user interface is a Web Browser (e.g. Internet Explorer and/orNetscape™ Navigator browser). The client agent 1508 can use any type ofprotocol, such as a remote display protocol, and it can be, for example,an HTTP client agent, an FTP client agent, an Oscar client agent, aTelnet client agent, an Independent Computing Architecture (ICA) clientagent from Citrix Systems, Inc. of Fort Lauderdale, Fla., or a RemoteDesktop Protocol (RDP) client agent from Microsoft Corporation ofRedmond, Wash. In some embodiments, the client agent 1508 is configuredto connect to the remote machine 30. In some embodiments (not shown),the client 1508 includes a plurality of client agents 1508, each ofwhich may communicate with a remote machine 30, respectively.

Additionally, the remote machine 30 may comprise a server agent 1528which may be capable of and configured to work in conjunction with theclient agent 1508. For example, the server agent 1528 may be a serverside component that accepts connections and requests from the clientagent 1508. In another embodiment, the server agent 1528 may be capableof and configured to accept or establish remote access connections orsessions for the client machine 10. In one embodiment, the client agent1508 and server agent 1528 may communicate using a protocol, such ashttp, ICA or RDP, over the network 1504. In some embodiments, the clientagent 1508 and/or server agent 1528 are used to establish, re-establish,maintain, or otherwise provide a server-based computing or thin-clientcomputing based connection or session. In another embodiment, the clientagent 1508 and the server agent 1528 establish the start and end pointsof communications for a connection between the client machine 10 and thedestination remote machine 30.

In some embodiments, the remote machine 30 includes a storage element1525 for storing the display layout. In one embodiment, storage element1525 provides the display layout 1520 as a globally mapped data file,which may be accessible by any of the applications 1530 of the remotemachine 30. In some embodiments, the display layout 1520 is stored inthe same form as provided to or received by the remote machine 30.Although the storage element 1525 is illustrated on the remote machine30 in FIG. 15B, the client machine 10 may also include a storage element1525′, and in some embodiments, the client machine 10 stores the displaylayout 1520 in the client's storage element 1525′, and/or to the remotemachine's storage element 1525.

The remote machine 30 may also include a session login mechanism 1545,which may include any type and/or form of service, process, task orprogram, application, or executable instructions on the remote machine30 to handle and process login or session requests. The session loginmechanism 1545, or any portion thereof, may be provided via theoperating system of the remote machine 30. In one embodiment, thesession login mechanism 1545 includes the windows logon process,winlogon, a component of the Microsoft® Windows families of operatingsystems. As such, the session login mechanism 1545 may provideinteractive logon support, and may include a Graphical Identificationand Authentication dynamically linked library (DLL) referred to as theGINA, and any number of network providers. The session login mechanism1545 may include any interfaces, such as an application programminginterface (API) or dynamically linked libraries, i.e., a dII, to allowany resource, application, network or network provide gather obtain anyidentification and authentication information during a logon process.

The session login mechanism 1545 may perform an authentication processand password-updating operations for the operating system and/or for oneor more resources, programs, applications, networks, or networkproviders. In one embodiment, the session login mechanism 1545 providesauthentication services for the operating system, and in additionalembodiments, also provides authentication services for access toapplications 1530 to be executed on the remote machine 30 on behalf ofthe client machine 10, such as in a server-based or thin-clientcomputing model. Additionally, the session login mechanism 1545 maymonitor any mouse and/or keyboard activity related to logging on orsecure access of the remote machine 30, or any resource, application,network, or network provider. In some embodiments, the session loginmechanism 1545 may establish any initial services, processes, or tasksfor a user or session on the remote machine 30.

The remote machine 30 may execute or otherwise provide one or moreapplications 1530. The application 1530 can be any type and/or form ofsoftware, program, or executable instructions such as any type and/orform of web browser, web-based client, client-server application, athin-client computing client, an ActiveX control, or a Java applet, orany other type and/or form of executable instructions capable ofexecuting on client machine 10 or communicating via a network 1504. Theapplication 1530 can use any type of protocol and it can be, forexample, an HTTP client, an FTP client, an Oscar client, or a Telnetclient. In some embodiments, the application 1530 uses a remote displayor presentation level protocol. In other embodiments, the application1530 comprises any type of software related to Voice-Over-InternetProtocol (VoIP) communications, such as a soft IP telephone. In furtherembodiments, the application 1530 comprises any application related toreal-time data communications, such as applications for streaming videoand/or audio. In some embodiments, the application 1530 provides one ormore windows 1535 a-1535 n, also sometimes collectively referencedherein as 1535.

In some embodiments, the remote machine 30 or a machine farm 38 may berunning one or more applications 1530, such as an application 1530providing a thin-client computing or remote display presentationapplication. In one embodiment, the remote machine 30 or machine farmexecutes as an application 1530, any portion of the Citrix Access Suite™by Citrix Systems, Inc., such as the MetaFrame or Citrix PresentationServer™, and/or any of the Microsoft® Windows Terminal Servicesmanufactured by the Microsoft Corporation. In one embodiment, theapplication 1530 is an ICA client, developed by Citrix Systems, Inc. ofFort Lauderdale, Fla. In other embodiments, the application 1530includes a Remote Desktop (RDP) client, developed by MicrosoftCorporation of Redmond, Wash.

Additionally, the remote machine 30 may run an application 1530, whichfor example, may be an application server providing email services suchas Microsoft Exchange manufactured by the Microsoft Corporation ofRedmond, Wash., a web or Internet server, or a desktop sharing server,or a collaboration server. In some embodiments, any of the applications1530 may comprise any type of hosted service or products, such asGoToMeeting™ provided by Citrix Online Division, Inc. of Santa Barbara,Calif., WebEx™ provided by WebEx, Inc. of Santa Clara, Calif., orMicrosoft Office LiveMeeting provided by Microsoft Corporation ofRedmond, Wash.

Although in FIG. 15A and FIG. 15B, the window processing mechanism 1550is illustrated as included in the application 1530, the windowprocessing mechanism 1550 may reside in any portion of the remotemachine 30, the client machine 10, and/or external to the application1530, for example, as illustrated in FIG. 15C. In one embodiment, thewindow processing mechanism 1550 comprises a service, process, or taskthat runs in a system context or with the system privileges of theoperating system. In some embodiments, the windows processing mechanism1550 may monitor messages 1540 communicated to windows 1535 a-1535 n ofan application 1530, and intercept and modify the message 1540 to thewindows 1535 a-1535 n. One ordinarily skilled in the art will recognizeand appreciate that the windows processing mechanism 1550 may compriseany type and/or form of executable instructions capable of performingthe operations described herein.

In another embodiment of illustrated in FIG. 15C, the session loginmechanism 1545 may be used to provide for, or use, any of thefunctionality of the window processing mechanism 1550. In someembodiments, the session login mechanism 1545 may read, access, acquireor otherwise obtain the display layout 1520 from the storage element1525. In other embodiments, the session login mechanism 1545 accesses,loads, or uses the functionality of the window processing mechanism 1550via a dynamically loaded library, such as a library provided via anetwork provider to the winlogon process of a WINDOWS operating system.In other embodiments, the session login mechanism interfaces with orcommunicates to the window processing mechanism 1550 to provide thetechniques described herein. In further embodiments, the session loginmechanism 1545 may use the techniques described herein duringreconnection, re-establishment, and/or re-authentication of a login oruser session, such as a remote session in a server-based computingenvironment 1500.

In another aspect, techniques for virtualizing a display environment ofa client machine 10 by controlling or directing the appearance, behaviorand attributes of a window 1535 of an application 1530 based on thedesired display layout 1520 for a client machine 10 are described. Inview of the systems and structure of the environments 1500, 1501, and1502 depicted in FIGS. 15A-15C, the operations, functionality, andtechniques will be addressed by the methods depicted in FIGS. 3A-3D.FIG. 3A depicts a method 300 for practicing an embodiment using thewindow processing mechanism 1550. FIG. 3B depicts examples of windowmessages and processing used in conjunction with the method 300. FIG. 3Cdepicts a method 350 for practicing an embodiment when reconnecting,re-establishing or re-authenticating via the session login mechanism1545. FIG. 3D depicts illustrative method 360 for changing the client'sdisplay layout 1520, for example, during execution of an application1530.

Referring now to FIG. 16A, in brief overview, one embodiment of a methodfor providing a desired display layout 1520 of the client machine 10 isshown. At step 1610, and at step 1615, the display layout 1520 is storedin the storage element 1525, and the display layout 1520 is associatedwith the client 1505. At step 1620, the window processing mechanism 1550accesses the display layout 1520 from the storage element 225 to obtainthe desired display layout information for the client machine 10. Atstep 1625, the window processing mechanism 1550 intercepts messages 1540to a window 1535 displayed on a client machine 10 by an application1530. At step 1630, the window processing mechanism 1550 modifies themessage 1540 to provide the window 1535 on the client machine 10 basedon the desired display layout 1520 for the client machine 10. At step1635, the window 1535 is displayed on the client machine 10 based on themodified message 1540. As such, the appearance and behavior of thewindow 235 is translated to and based on the display layout 1520.

In further detail, at step 1610 of the method, the desired displaylayout 120 for the client is provided. In one embodiment, the displaylayout 120 is communicated from the client machine 10 to the remotemachine 30. For example, the client machine 10 establishes a connectionor communication session with the remote machine 30. In some cases, theremote machine 30 requests the display layout 1520 from the clientmachine 10, and the client 1505 communicates the display layout 1520 inresponse to the request. In another embodiment, the display layout 1520is communicated via the session login mechanism 1545 during a logon orauthentication process, and in some embodiments, upon a re-logon orre-authentication process. In one embodiment, the display layout 1520 isstored in a database and queried by the client machine 10 or remotemachine 30 to obtain the display layout 1520. In other embodiments, thedisplay layout 1520 is downloaded, by either the client machine 10 orthe remote machine 30 from a web server, a web-site, an applicationserver, another remote machine 30′ or via the Internet. In furtherembodiments, a user may configure the display layout 1520 with aprogram, application, or tool, and store the display layout 1520 on aclient machine 10, remote machine 30, or another client machine 10.

At step 1615, the display layout 1520 is stored in the storage element1525, and associated with the client machine 10. In some embodiments,the remote machine 30 receives the display layout 1520 from the clientmachine 10 and stores the display layout 1520 in the storage element1525. In one embodiment, the remote machine 30 stores the display layout1520 as a globally mapped data file on the remote machine 30 accessibleby one or more applications 1530. In another embodiment the remotemachine 30 stores the display layout 1520 to another client machine 10accessible to the remote machine 30, such as via the network 1504. Insome embodiments, the client machine 10 stores the display layout 1520to a storage element 1525 on the remote machine 30, to a storage element1525 on the client machine 10, or to a storage element 1525 accessiblevia the network 1504 or via the Internet.

The display layout 1520 may be stored to the storage element 1525 in anyform suitable to the storage element 1525, and may be converted,transformed, altered, translated or otherwise processed for storage inthe storage element 1525. For example, in one embodiment, the displaylayout 1520 may comprise data, such as a file, on the client machine 10transmitted via network packets to the remote machine 30, and thentranslated into a globally mapped data file on the remote machine 30. Inanother embodiment, the display layout 1520 is stored into any typeand/or form of database 1525, such as a relational database. In otherembodiments, the display layout 1520 is stored in storage 1525comprising memory. For example, the display layout 1520 may comprise orbe represented by any type of object, data structure, or portion ofmemory on the client machine 10 and/or remote machine 30.

The display layout 1520 may be associated with the client machine 10 byany suitable means and/or mechanisms. In one embodiment, the name, orany portion thereof, of the globally mapped data file may identify theclient machine 10. In another embodiment, any portion of content of theglobally mapped data file may identify the client machine 10. Inadditional embodiments, the client machine 10 or remote machine 30 mayuse any type of object, data structure, process, or other elements inmemory to associate the display layout 1520 with the client machine 10.In other embodiments, the client machine 10 or remote machine 30 may useportions of the storage element 1525 or other types of storage, such asanother file, to associate the display layout 1520 with the client.

The window processing mechanism 1550, at step 1620 of illustrativemethod 300, accesses the display layout 1520 from the storage element1525 to obtain the desired display layout information for the clientmachine 10. In one embodiment, the executable instructions of the windowprocedure used by the window processing mechanism 1550 comprisesinstructions to load, read, or otherwise acquire the display layout1520. For example, the window processing mechanism 1550 may perform anytype and/or forms of file input/output, i.e., file I/O, operations toread a globally mapped data file having the display layout 1520. Inanother embodiment, the instructions of the hooking applicationprogramming interface (API) for the window processing mechanism 1550provides instructions for obtaining the display layout 1520. In anotherembodiment, the application 1530 reads or accesses the display layout1520, for example, upon execution or start up. In some embodiments, theapplication 1530 may be executed during a session, such as a user orremote session. In one embodiment, the globally mapped data file 1525may only be accessible by an application 1530 associated with oravailable via the remote session. In further embodiments, access to theglobally mapped data file may have access locked by a mutex orsemaphore, which is global for the remote session. One ordinarilyskilled in the art will recognize and appreciate that any type and/orform of locking mechanism can be used to control access the storageelement 1525, such as a globally mapped data file.

At step 1625, the window processing mechanism 1550 intercepts messages1540 to a window 1535 displayed on a client machine 10 by an application1530. In one embodiment, upon obtaining the display layout 1520 ahooking mechanism is introduced into the remote machine 30 or theapplication 1530 on the remote machine 30, which hooks one or morewindow creation application programming interfaces (APIs), such as forexample, a create window type of API in a WINDOWS based environment. Insome embodiments, the window processing mechanism 1550 intercepts allmessages 1540 to windows 1535 of the application 1530. In otherembodiments, the window processing mechanism 1550 intercepts messages1540 of a certain message identifier or name. In one embodiment, themessage 240 may have arguments, parameters or values that are used bythe window processing mechanism 1550 to determine that the message 1540should be intercepted. In additional embodiments, the window processingmechanism 1550 intercepts messages 1540 to some of the windows 1535 ofthe application 1530, and in further embodiments, only for a portion ofthe types of messages 240 communicated to these windows 1535. In yetanother embodiment, the window processing mechanism 1550 isconfigurable, for example, by a user, to select the messages 1540, byname, type, or otherwise, to be intercepted.

In some embodiments, the window processing mechanism 1550 interceptsmessages 1540 communicated to or intended for a top-level window 1535 ofthe application 1530. In other embodiments, the window processingmechanism 1550 may intercept any level of window 1535, or only certainlevels of windows 1535 in a hierarchy of windows 1535. For example, thewindow processing mechanism 1550 may ignore any popup dialog windows ofa second level window displayed on top of or in front of a top-levelwindow 1535.

In one embodiment, the window processing mechanism 1550 may intercept amessage 1540 but pass the message 1540 through or communicate themessage 1540 to the original or replaced window procedure. In someembodiments, the window processing mechanism 1550 ignores certainmessages 1540. In another embodiment, the window procedure of the windowprocessing mechanism 1550 also includes the functionality and operationsof the replaced window procedure. As such, the window processingmechanism 1550 may intercept a message 1540 and have either the replacedwindow procedure or the window procedure hooked into the application1540 process the message 1540.

At step 1630, the window processing mechanism 1550 modifies the message1540 to provide the window 1535 on the client machine 10 based on thedesired display layout 1520 for the client machine 10. In someembodiments, the window processing mechanism 1550 examines, inspects,analyzes, or otherwise processes any values, arguments, or parameters ofthe message 1540 in comparison to the display layout 1520 for the clientmachine 10 displaying the application 1530. Based on the comparison, thewindow processing mechanism 1550 may modify, adjust, edit, change,alter, replace, translate or otherwise set or provide values, arguments,and/or parameters for the message 1540 that will provide the desiredbehavior, appearance and attributes of the window 235 as displayed or tobe displayed by the application 1530 on the client machine 10 inaccordance with the display layout 1520. For example, the values and/orparameters of the message 1540 may indicate a size, position, location,resolution or other attributes of the window 1535. These characteristicsmay be based on a display environment different than as specified in thedisplay layout 1520. As such, in some embodiments, the window processingmechanism 1550 may modify the size, position, location, resolution orother attributes of the message 1540 for a display 1522 a-1522 nspecified in the display layout 1520.

By way of further example, and referring now to FIG. 16B, the windowprocessing mechanism 1550 may intercept and modify a message 1540identified as one of the following: 1) WM₁₃ GETMAXMININFO, 2) WM₁₃WINDOWPOSCHANGING, 3) WM₁₃ WINDOWPOSCHANGED, and 4) WM₁₃ DISPLAYCHANGE.At illustrative step 1630 a, for a message 1540 intercepted andidentified as a WM₁₃ GETMINMAXINFO, the window processing mechanism 1550analyzes the position of the application 1530, i.e., a top-level window1535, relative to the one or more displays 1522 a-1522 n of the displaylayout 1520, and determines which of the displays 1522 a-1522 n theapplication 1530 should be maximized to. The window processing mechanism1550 modifies the message 1540 to provide values corresponding andtranslated to the resolution based on the desired display layout 1520.For example, a remote machine 30 may provide window resolution for asingle monitor session, and the window processing mechanism 1550translates the resolution to the multiple display environment providedvia the display layout 1520. As such, this technique enables theapplication 1530 to maximize to a desired location in accordance withthe display layout 1520, instead of the single monitor session.

At illustrative step 1630 b, for a message 1540 intercepted andidentified as WM₁₃ WINDOWPOSCHANGING, the window processing mechanism1550 determines if the window 1535 is in the maximized state, and if so,the message 1540 is modified to set the window flag to a no move styleof window, or otherwise to fix the location or position of the window1535, or not allow the position of the window 1535 to change. As such,in the maximized state a user may not be able to move the window 1535.This technique enables the application 1530, or a window 1535 of theapplication 1530 to be maximized to a set or fixed location on a display1522 a-1522 n specified by the display layout 1520. In some embodiments,either in response to the WM₁₃ WINDOWPOSCHANGING message 1540 orotherwise, the window processing mechanism 1550 determines the window1535 is not in the maximized state, and modifies the message 1540 toremove the no move style, e.g., the window's position is no longerfixed, or to otherwise allow the position of the window 1535 to bemoved.

At illustrative step 1630 c, for a message 1540 intercepted andidentified as WM₁₃ WINDOWPOSCHANGED, the window processing mechanism1550 compares the position or location of the window 1535 to the displaylayout 1520 and if the window 1535 is to be rendered outside the screenor work area of display 1522 a-1522 n, then the position or location ofthe window 1535 is changed to be rendered in at least a portion of thescreen or work area of the display 1522 a-1522 n. This technique enablesthe user not to lose the application 1530 or window 1535 of theapplication 1530 to an off-screen location.

At illustrative step 1630 d, for a message 1540 intercepted andidentified as WM₁₃ DISPLAYCHANGED, the window processing mechanism 1550suspends passing of messages 1540 until a new or second display layout1520 is obtained or provided for the client 1505. In one embodiment, thewindow processing mechanism 1550 suspends the processing of all messages1540. In some embodiments, the window processing mechanism 1550 suspendsmessages 1540 that are intercepted and communicated to the replaced ororiginal window procedure. In other embodiments, the window processingmechanism 1550 suspends messages for the replaced or original windowprocedure while continuing to process other messages 1540. Thistechnique enables a client machine 10 to dynamically change the displaylayout 1520 at any time, for example, during the execution of anapplication 1530.

Although the techniques of are generally described above in relation tomessage, one ordinarily skilled in the art will recognize and appreciatethat any message of any type and/or form may be used. Furthermore, thewindow processing mechanism 1550 may perform any logic, function,operations or rules based on the message 1540 and/or the display layout1520, and even for the same type of message 1540, may perform adifferent operation or function for each instance of the message 1540depending on changes to the display layout 1520 or any events,conditions or status of the environment 1500, 1501 or 1502.

Referring back to FIG. 16A, at step 1635 of method 300, the window 1535is displayed on the client machine 10 based on the message 1540processed via the window processing mechanism 1550. As such, when thewindow processing mechanism 1550 modifies the message 1540 based on thedisplay layout 1520, the window 1535 is displayed on the client machine10 according to the display layout 1520. In some embodiments, the windowprocessing mechanism 250 does not modify the message 1540, andtherefore, the window 1540 is displayed on the client machine 10according to the unmodified message 1540. The technique as illustratedabove enables, for example, in one embodiment of a server-basedcomputing environment 1500, an application 1530 running on remotemachine 30 to provide display output to the client machine 10 thatcontrols and directs the behavior, appearance, and attributes of windowsin the display output in any manner desired and specified by the displaylayout 1520, which may not correspond to the physical display layout ofthe client machine 10.

In another aspect, although techniques described herein are generallydescribed with a window management system from WINDOWS operating system,one ordinarily skilled in the art will recognize and appreciate thattechniques described herein may be practiced with any type and/or formof window manager or management system, such any type and/or form ofX-windows managers, including any custom or open-source based windowmanager running on any type of operating system.

Referring now to FIG. 16C, these techniques may be practiced during there-connection, re-establishment or re-authentication of anycommunication session or user session, for example a remote displaysession between the client machine 10 and the remote machine 30. In oneembodiment, the session login mechanism 1545 as illustrated on theremote machine 30 of FIGS. 15A and 15B may include the window processingmechanism 1550, or any portion thereof. In brief overview of method 350,the session login mechanism 1545, at step 1652, accesses or obtains thedisplay layout 1520 from the storage element 1525. At step 1654, theremay be a disconnection and reconnection processed by the session loginmechanism 1545. Upon re-establishing and/or re-authenticating thesession, the session login mechanism, at step 1656, compares a locationof a window 1535 to the client's display layout 1520, and at step 1658,modifies the window 235 to display on the client machine 10 based on theclient's display layout 1520.

At illustrative step 1652, the session login mechanism 1545 obtainsinformation on the display layout 1520 by any suitable means and/ormechanisms. For example, the window processing mechanism 1550 includedin or used by the session login mechanism 1545 may have executableinstructions, such as file I/O operations, to access a globally mappeddata file 1525. In another embodiment, the session login mechanism 1545may load dynamically linked libraries that load, read or otherwiseaccess the storage element 225 having the display layout information. Inone embodiment, as part of establishing or re-establishing the session,the session login mechanism 1545 may obtain the display layout 1520 fromthe client 1520. For example, the session login mechanism 1545 requeststhe display layout 1520 from the client machine 10 along with anyidentification or authentication credentials.

At illustrative step 1654, any type of disconnection or disruption to asession between the client machine 10 and remote machine 30 may occur,and any type of reconnection or re-establishment of the session may befacilitated via the session login mechanism 1545. In some cases, a usermay cause a disconnection or disruption, temporary or otherwise, to asession between the client machine 10 and the remote machine 30 due tophysical changes in the client's display environment or because the usermoves to another client machine 10. In one case, the user moves from afirst client machine 10 a, such as a work computer, to a second clientmachine 10 b, such as a home computer. The remote machine 30 maymaintain the same user session between computing devices 100 a-110 b butthe display layout 1520 may have changed. In another case, the userand/or the client machine 10 may traverse network segments or networkaccess points that cause changes in the network address or host name,e.g., internet protocol (IP) address, of the client machine 10 or causesthe client machine 10 to disconnect. The client machine 10 mayreconnect, manually or automatically, to the network 1504, such as viathe client agent 1508. As such, the session login mechanism 1545 mayfacilitate or be used to facilitate the reconnection.

At step 1656 of method 350, the session login mechanism 1545 comparesthe location or position of a window 1535 of an application 1530 inrelation to the desired display layout 1520. In some embodiments, thesession login mechanism 1545 intercepts a message 1540 to a window 1535,and examines, inspects or analyzes any portion of the message 1540, suchas a value or parameter. In one embodiment, the session login mechanism1545 queries, acquires or obtains the current location or position ofone or more windows 1535 of the application 1530 via an applicationprogramming interface (API). In another embodiment, the session loginmechanism 1545 requests from the application 1530, the location orposition of any of the application's windows. The session loginmechanism 1545 compares the location, position, size, and any otherattributes of the window 1535 to any information in the display layout1520.

At step 1658, the session login mechanism 1545 may modify the window1535 based on the desired display layout 1520. From the comparison ofthe information about the window 1535 to the information of the displaylayout 1520, the session login mechanism 1545, in some embodiments,modifies the window 1535 to display on the client machine 10 via adisplay 1522 a-1522 n identified in the display layout 1520 in a desiredmanner. In one embodiment, via the functionality of the windowprocessing mechanism 1550 embodied in or interfaced with the sessionlogin mechanism 1545, a message 1540 to a window 1535 may be interceptedand modified in accordance with the operations described herein. Inanother embodiment, the session login mechanism 1545 may modify one ormore windows 1535 of the application 1530 via any applicationprogramming interface (API) to modify such windows 1535. The techniquesdepicted by method 350 enable client sessions to be disconnected andreconnected and have the display of windows be adjusted accordingly toany new or changed display environments of the client machine 10, new orchanged display layouts 1520 of the client machine 10, or changes fromone client machine 10 a to another client machine 10 b.

In another aspect, dynamically changing a display layout 1520 for aclient machine 10 is described. Referring now to FIG. 16D, thetechniques described may be practiced for a change to a display layout1520 that occurs during the execution of an application 1530. In briefoverview of illustrative method 360, at step 1662, a client's displaylayout 1520 is changed. At step 1664, the window processing mechanism350 suspends window message processing when the client's display layout1520 is changed. At step 1666, an updated or a second display layout1520′ is obtained by the window processing mechanism 1550, and at step1668, the window processing mechanism 1550 resumes intercepting andmodifying messages 1540 to windows 1535 based on the second displaylayout 1520′.

In further detail, at step 1662, the display layout 1520 may be changedat any time and for any reason. In one embodiment, the displayenvironment for the client machine 10 may change and the display layout1520 may be updated to reflect the changed display environment. Forexample, another display device 124 may be connected to the clientmachine 10. In another embodiment, a user of the client machine 10 maybe making adjustments, updating or otherwise changing the display layout1520 to suit the user's desire for a behavior and appearance ofapplications 1530 and the display of windows 1535 of the application1530 on the client machine 10. In yet a further embodiment, a firstsession may be on a first client machine 10 with a first display layout1520, and the user switches to a second session or maintains the firstsession on a second client machine 10′ with a second or updated displaylayout 1520′.

At step 1665, the method suspends intercepting and modifying messages1540 for windows 1535 of an application 1530 upon notification of achange to the display layout 1520. In one embodiment, the windowprocessing mechanism 1550 intercepts a message 1540, such as the WM₁₃DISPLAYCHANGE message, indicating a change in any attribute orcharacteristic, for example, the resolution, of the display environment.In another embodiment, the client machine 10 communicates a notice tothe remote machine 30, the window processing mechanism 1550 or thesession login mechanism 1545 indicating a change has occurred or isabout to occur to the display layout 1520. In yet another embodiment,the application 1530 may comprise a user interface mechanism for a userto indicate a change to the display environment, or to have theapplication 1530 suspend processing of window messages according to thedisplay layout 1520.

The window processing mechanism 1550 may suspend the processing ofmessages 240 for all applications 230, a portion of applications 230, orfor a portion of windows 235 of one, some, or all of the application230. In one embodiment, the window processing mechanism 1550 queues anymessages 240 received until the window processing mechanism 1550 obtainsanother display layout 1520. In another embodiment, the windowprocessing mechanism 1550 only suspends processing of window messages tobe modified according to the display layout 1520, and continues passingthe messages 240 not to be modified to the original or replaced windowprocedure.

At step 1666 of the method, an updated or a second display layout 1520′is obtained to use for window message processing. The updated or seconddisplay layout 1520′ may be provided by any suitable means and/ormechanisms. In one embodiment, the updated or second display layout1520′ is stored with the first display layout 1520 in the storageelement 225. In another embodiment, the updated or second display layout1520′ is stored as an updated version of the first display layout 1520,and in further embodiments, the second display layout 1520′ may replacethe first display layout 1520 in the storage element 225. In oneembodiment, the client machine 10 communicates the updated or seconddisplay layout 1520′ to the remote machine 30 or stores the seconddisplay layout 1520′ to the storage element 225 on the remote machine30. In some embodiments, the client machine 10 via a reconnection orre-establishment to the remote machine 30 may provide an updated displaylayout 1520. In one embodiment, the client machine 10 communicates anunchanged display layout 1520 or a display layout 1520 to the remotemachine 30 that the remote machine 30 already has stored in the storageelement 225. In yet other embodiments, the remote machine 30 or clientmachine 10 may obtain the second display layout 1520′ from anotherclient machine 10 on the network 204, such as downloading the seconddisplay layout 1520′ form a remote machine 30. As described above inconnection with illustrative method 300, the window processing mechanism350 may obtain the display layout 1520 from the storage element 225 by avariety of means and/or mechanisms.

At step 1668 of method 360, the window processing mechanism 1550 resumesintercepting and modifying messages 240 to windows 235 based on thesecond display layout 1520. In one embodiment, if the window processingmechanism 1550 queued any messages 240, the window processing mechanism1550 analyzes and modifies the queued messages 240 based on the seconddisplay layout 1520′. Otherwise, the window processing mechanism 1550uses the second display layout 1520′ to modify any messages 240intercepted after obtaining the second display layout 1520′. Using thetechniques described herein, a client display environment and a client'sdisplay layout can be dynamically changed during the course of executingone or more applications, and the display of windows for the applicationappear and behave according to the changes to the display layout. Forexample, another display device may be added to the client, and anapplication may be minimized during a change in the display layout. Whenthe display layout is updated, the user can maximize the application andhave the application appear in the appropriate display even though thedisplay environment changed when the application was minimized.

In view of the functions, structures, and operations described above,systems and methods are provided to control and direct the appearance,behavior and attributes of windows of an application in a flexiblemanner for virtualizing, simulating or providing a multiple displayenvironment without restricting or limiting the client side displayconfiguration. For example, the display layout of the client may not belimited to configure the physical monitor of the client as the primarydisplay, i.e. as the top left most monitor in the display layoutconfiguration. The systems and methods described may be practiced in aserver-based or thin-client based computing environment, with clientshaving multiple display devices, or with clients having a single displaydevice. Additionally, the configuration of a display layout that is notrestricted or limited to the physical display environment of the clientis provided. The display environment of the client may extend to includeadditional virtual displays, so if the client has two display devices,three or more displays may be virtualized or simulated for the client. Asingle display configuration for a single display device may beimplemented while still changing the appearance and behavior of windowsbased on a desired or customized display layout. A client or user maygain the functionality, benefits, and advantages of a multiple displayenvironment without having multiple display devices, or having all thedisplay devices desired.

In one embodiment, multi-monitor support provides maximizing of windowsto fill a single monitor rather than the full screen and centering ofdialogs on a monitor rather than on a screen. In another embodiment thesession management component, the virtual machine service component, anda multi-monitor hook component executing in a computing environmentprovided by a virtual machine together provide multi-monitor support ina virtual machine environment. In still another embodiment, amulti-monitor hook component and a component acquiring client geometrydata provide multi-monitor support in a virtual machine environment.

In one embodiment, the session management component 1300 reads themonitor configuration for the client machine 10 from a multi-monitorhook file mapping. In some embodiments where a user of the clientmachine 10 establishes a connection to a presentation server executingon an execution machine in which the virtual machine provides access toa computing environment, the presentation server generates themulti-monitor hook file mapping upon establishment of the connection bythe user.

In one embodiment, the session management component 1300 sends a messageto the virtual machine service component containing the monitor layoutfor the user. In some embodiments, the message is sent when the sessionmanagement component 1300 detects a user reconnection, so that themonitor layout remains synchronized with the client machine 10.

The virtual machine service component receives the monitor layoutmessages provided by the session management component 900. In someembodiments, the virtual machine service component creates a filemapping in the computing environment and updates the file to includemonitor layout data.

In other embodiments, the virtual machine service component also createsa checksum for the data that is used by the multi-monitor hook componentto ensure that it has correctly read the layout data. In one of theseembodiments, a checksum is used rather than a locking scheme tosynchronize access to the layout data. In this embodiment, the checksumdoes not cause any blocking between the processes reading the data. Thelayout data is updated infrequently and may be small in size, so thechecksum calculation may complete quickly. In another of theseembodiments, the reader processes save the checksum, read the data andrecalculate the checksum. If the calculated checksum does not match thesaved checksum it indicates that the data was updated while it was beingread and the process is repeated. As the data is usually only updatedwhen the user reconnects to another client and given the short timerequired to read the data, it is unlikely that a reader would have toreread the data more than once for a particular change. In someembodiments, the virtual machine service component uses a stored defaultdisplay setting for the client machine 10, the stored default selectedto ensure that the computing environment has valid display settings uponinitialization of the session.

In some environments, a multi-monitor hook component executes in acomputing environment provided by a virtual machine. In one of theseembodiments, the multi-monitor hook component receives an event for eachwindow created just before the window is created, including a windowhandle for the window being created. The multi-monitor hook componentmay identify a window type of the window and determine to hook windowmessages for the window. In some embodiments, windows having windowtypes indicating that the window can be maximized or that the window isa dialog will be hooked. Hooked windows may be added to an array thatcontains the window handle and an original window procedure. In otherembodiments, the multi-monitor hook component receives an eventindicating that a window is about to be destroyed. In one of theseembodiments, the multi-monitor hook component removes the entry in thehook array associated with the window.

In some embodiments, the multi-monitor hook component receives anidentification of a window after the window is created and before thewindow is displayed. In one of these embodiments, the multi-monitor hookcomponent checks the position of the dialog and if it spans multiplemonitors, the multi-monitor hook component repositions the window to thecenter of the monitor that contains most of the dialog, or the firstmonitor containing the dialog if the dialogs area is equally splitbetween two monitors. In other embodiments, the multi-monitor hookcomponent receives an event when a window is about to be maximized. Themulti-monitor hook component ensures that when the window is maximizedfrom the minimized state it will be positioned on the correct monitor.

In some embodiments, the multi-monitor hook component receives an eventwhen a window is being maximized. The multi-monitor hook componentchecks the state of the window and, if the window is minimized, themulti-monitor hook component retrieves an identification of a monitor inwhich the window is minimized from the window hook array. If the windowis not minimized, the multi-monitor hook component identifies themonitor that contains most of the window. If no monitor is found, or ifthe monitor does not exist (as after a reconnection) monitor 0 is used.The multi-monitor hook component then removes the origin and size of themonitor from its saved monitor information and updates the MINMAXINFOstructure pointed to by the message. This causes the window to maximizeto the specified monitor only.

In some embodiments, the virtual machine service component receivesauthentication information associated with a user of the client machine10. In one of these embodiments, the virtual machine service componentreceives the authentication information from a protocol stack componentreceiving the credentials from the client machine 10. In another ofthese embodiments, the virtual machine service component receivesauthentication information from the session management component 1300.Instill another of these embodiments, the virtual machine servicecomponent uses the received authentication information to authenticatethe user of the client machine 10 to the computing environment providedby the virtual machine.

In one embodiment, when the communications channel is established andthe initial session related information is passed to the virtual machineservice component, the virtual machine service component automaticallylogs the user into the computing environment. In one embodiment, thevirtual machine service component receives credentials from the sessionmanagement component 1300. In another embodiment, the virtual machineservice component receives credentials previously provided by the user.In some embodiments, the user provides credentials to the client machine10 prior to requesting access to a resource. In one of theseembodiments, the user provides credentials to a client agent, such as anICA client. The virtual machine service component automaticallyreconfigures the display settings of the guest operating system to matchthose of the ICA client. The virtual machine produces graphics and soundoutput to the virtual devices that redirect that output to a clientagent, such as an ICA client, on the requesting machine. The virtualmachine receives audio input, mouse and keyboard device data redirectedfrom the ICA client. When the virtual machine is shutdown or suspendedthe session management component 1300 cleans up and shuts down the ICAsession.

The remote machines 30, 30′, and 30″ can belong to the sameauthentication domain. A domain may comprise a group of machines, suchas application servers, execution machines, or client nodes undercontrol of one security database. A domain can include one or moremachine farms linked together to act as a single system to providecentralized administration. Conversely, a machine farm can include oneor more domains. For servers of two different domains to belong to thesame machine farm, a trust relationship may need to exist between thedomains. A trust relationship is an association between the differentdomains that allows a user to access the resources associated with eachdomain with just one log-on authentication.

In one embodiment, the remote machine 30′″ is in a different domain thanthe farm 38. In another embodiment, the remote machine 30′″ is in thesame domain as machines 30, 30′, and 30″. For either embodiment,machines 30, 30′, and 30″ can belong to one server farm, while theremote machine 30′″ belongs to another machine farm, or all of themachines 30, 30′, 30″ and 30′″ can belong to the same machine farm. Whena new machine is connected to the network 150, the new machine eitherjoins an existing machine farm or starts a new machine farm.

The machines 10 may be in a domain, or may be unconnected with anydomain. In one embodiment, the client machine 10 is in the domain 38. Inanother embodiment, the client machine 10 is in another domain that doesnot include any of the machines 30, 30′, 30″ and 30′″. In anotherembodiment, the client machine 10 is not in any domain.

In one embodiment the client machine 10 is in the domain 38 and a userof the machine provides user credentials to log onto the client machine10. User credentials typically include the name of the user of themachine, the password of the user, and the name of the domain in whichthe user is recognized. The user credentials can be obtained from smartcards, time-based tokens, social security numbers, user passwords,personal identification (PIN) numbers, digital certificates based onsymmetric key or elliptic curve cryptography, biometric characteristicsof the user, or any other means by which the identification of the userof the client node can be obtained and submitted for authentication.

From the user-provided credentials, the client machine 10 generates userauthentication data. The client machine 10 transmits this userauthentication data to the remote machine 30. In this embodiment, theuser credentials are not transmitted over a network, only the resultinguser authentication data is transmitted by the client machine 10.

The remote machine 30 may determine which resources hosted by themachine farm containing remote machine 30 are available for use by theuser of the client machine 10. In one embodiment, the remote machine 30consults user authentication data to make this determination. In anotherembodiment, the remote machine 30 consults information associated with aresource requested by the user to make the determination. The remotemachine 30 transmits information representing the available resources tothe client machine 10.

The user authentication performed by the remote machine 30 can sufficeto authorize the use of each hosted resource presented to the clientmachine 10, although such resources may reside at another machine.Accordingly, in this embodiment, when the client machine 10 accesses orlaunches (i.e., initiates execution of) one of the hosted resources,additional input of user credentials by the user will be unnecessary toauthenticate access to that resource. Thus, a single entry of the usercredentials can serve to determine the available resources and toauthorize the access or launching of such resources without anadditional, manual log-on authentication process by the user.

FIG. 17 depicts in more detail a system for remotely authenticating aclient of a client machine 10 to a remote machine 30. As shown in FIG.17, the client machine 10 includes an authentication module 1710 incommunication with a thin-client program 1720. The authentication module1710 receives user authentication credentials provided for the purposesof authenticating a user to the client machine 100, the remote machine30, or both. Received authentication credentials can includeusername-password combinations, graphical password data, data derivedfrom time-based tokens such as the SecurlD line of tokens manufacturedby RSA Security Inc. of Bedford, Mass., challenge-response data,information from smart cards, and biometric information such asfingerprints, voiceprints, or facial features. The authentication module1710 may use the provided authentication credentials to authenticate theuser to the machine 100. For example, in WINDOWS-based environments, theauthentication module 1710 may be provided by the MSGINAdynamically-linked library. In other embodiments, for example, inUnix-based environments, the authentication module 1710 may be providedby the Unix Pluggable Authentication Manager, using the pam₁₃ krbmodule. In still other embodiments, the authentication module 1710 maybe provided by the UNIX kinit command program.

In the embodiment shown in FIG. 17, the machine 100 also includes asecurity service 1712. In some embodiments, the authentication module1710 and the security service 1712 are provided as the samedynamically-linked library. The security service 1712 provides securityservices to modules and applications on the machine 100, including theauthentication module 1710 and the thin-client application 1720, such asauthentication to the machine 100 and authentication to remote machinesor network services. For example, the security service 1712, which maybe the GSSAPI specified by the Internet Engineering Task Force (IETF) orthe SSPI manufactured by Microsoft Corporation of Redmond, Wash., mayobtain a Kerberos ticket in response to receipt of the userauthentication credentials and use this ticket to obtain additionalKerberos tickets to authenticate the user to remote machines or networkservices, at the request of modules or applications on the machine 100.The security service 1712 may then generate user authentication datausing these Kerberos tickets if needed for remote authentication. In oneembodiment, the security service 1712 may generate the userauthentication data using an external authentication service, such as aKey Distribution Center in a Kerberos environment or Active Directory ina Windows-based environment.

The security service 1712 provides the generated user authenticationdata, e.g., Kerberos ticket and associated Kerberos authenticator, tothe thin-client application 1720. The thin-client application 1720transmits the user authentication data to a remote machine 30 for remoteauthentication of the user. Thus, unlike existing single sign-onmechanisms for server-based computing, user-provided authenticationcredentials are not transmitted over the network 150 to a remote machine30. The user authentication data generated by the security service 1712is independent of the method used by the user to authenticate to themachine 100. Thus, for example, a Kerberos ticket for the user ofmachine 100 is obtained whether the user uses a username-passwordcombination or a biometric to authenticate to the machine 100.

In the embodiment shown in FIG. 17, the thin-client application 1720communicates with the remote machine 30 via a thin-client protocolhaving one or more virtual channels 1735. In these embodiments, thethin-client application 1720 loads a virtual channel driver and uses itto send and receive messages on the authentication virtual channel. Insome embodiments, the virtual channel driver exposes functions foropening the virtual channel and sending data over it.

The thin-client application 1720 passes a data structure to the remotemachine 30 for the virtual channel 1735 when the thin-client protocolconnection is established, indicating to the server-side thin-clientapplication 1750 that the authentication virtual channel is available.In one embodiment, the virtual channel data structure for theauthentication virtual channel contains the virtual channel informationand a representation of the size of the largest data packet the machine100 can accept from or send to the remote machine 30 over the virtualchannel 1735. The data packet size is constrained by the maximumthin-client size and any specific memory restrictions imposed by theclient machine 10. In one particular embodiment, the data structure forthe authentication virtual channel is defined as: typedef struct _C2H {  VD_C2H Header;   UINT16 cbMaxDataSize; } C2H, *PC2H;

The server-side thin-client application 1750 indicates to thethin-client application 1720 its intention to perform authenticationusing the authentication virtual channel 1735 by opening the virtualchannel and sending a bind request message onto the channel. Once thevirtual channel has been opened, the virtual channel driver in thethin-client application 1720, in one embodiment, reads a messagerequesting a binding from the virtual channel, sends a message onto thevirtual channel responding to the bind request; and reads a “commit”message from the channel. In one embodiment, the message requesting abinding includes data specifying the protocol version that is supported.In other embodiments, the protocol version can be negotiated between thethin-client application 1720 and the server-side thin-client application1750 using the bind request and bind response messages.

The bind request, bind response, and bind commit initialization messagesallow the server-side thin-client application 1750 and the thin-clientapplication 1720 to conduct a 3-way handshake initiated by theserver-side thin-client application 1750, and negotiate capabilities. A2-way handshake may be initiated by the server-side thin-clientapplication 1750 when the current set of virtual channel capabilitiescan be negotiated using a 2-way handshake only, but a 3-way handshake issupported to allow more flexibility that might be required by newcapabilities or future enhancements to current capabilities. Forexample, in a3-way handshake, after receiving a “menu” of capabilitiesfrom the server-side thin-client application 1750, the thin-clientapplication 1720 can exhibit a specific preference or could insteadacknowledge a whole set of options pertaining to a specific capabilitythus letting the server-side thin-client application 1750 decide on aspecific option. In a 2-way handshake to be initiated by the thin-clientapplication 1720, the thin-client application 1720 could not exhibit aspecific preference because it might not be supported by the host.

Following channel setup, the virtual channel driver of both thethin-client application 1720 and the server-side thin-client application1750 does the following in a loop until a “stop” message or an “error”message is received: retrieve authentication data from the securityservice 1712, 1712′, providing as input any authentication data sent bythe other party via the virtual channel; and send the retrievedauthentication data (if any) onto the virtual channel in a data message.If the retrieval of data from the security service 1712, 1712′ returneda “STOP” message, then signal stop and close the authentication virtualchannel. In some embodiments the virtual channel driver may reset itselfon a “stop” signal. If the retrieval of data from the security service1712, 1712′ returned a “CONTINUE” message, then continue. If theretrieval of authentication data from the security service 1712, 1712′returned an “ERROR”, then signal that an error has occurred and closethe authentication virtual channel.

As long as “stop” or “error” are not signaled, the virtual channeldriver of the thin-client application 1720 and the server-sidethin-client application 1750 are free to exchange data messages untilthe security service 1712, 1712′ stops producing data buffers to besent. In some embodiments, the number of messages exchanged may belimited by the virtual channel driver, the server-side thin-clientapplication 1750, or the virtual channel 1735. In other embodiments, thevirtual channel driver of the thin-client application 1720 and theserver-side thin-client application 1750 exchange messages sequentially,that is, two messages are not sent in one direction without a reply tothe first being sent in the other. In either embodiment, messageexchange can stop after a message has been sent in either direction.

In some particular embodiments, the data messages are sent over thevirtual channel Least Significant Double Word (LSDW), Least SignificantWord (LSW), Least Significant Byte (LSB) first. In other particularembodiments, the data messages are aligned at a byte boundary and fullypacked in memory. In these embodiments, data fields will be aligned inmemory as written to or read from the virtual channel.

Some messages transmitted on the authentication virtual channel spanmultiple virtual channel packets. To support this, every message must bepreceded by a message specifying the length of the next transmittedcommand. An example of a message that may be used to specify the lengthof the next command is: typedef struct _PKT_CMDLEN {    UINT32 Length;   UINT8 Command;    UINT8 FlagsBitMask; } PKT_CMDLEN, *PPKT_CMDLEN;

In some of these embodiments, PKT₁₃ CMDLEN also contains a commandnumber to indicate what type of message is to follow: #defineCMD_BIND_REQUEST 0x00 #define CMD_BIND_RESPONSE 0x01 #defineCMD_BIND_COMMIT 0x02 #define CMD_SSPI_DATA 0x03

A PKT₁₃ CMDLEN packet containing Length=0 indicates that no more datawill follow (i.e. a logical channel close).

The server-side thin-client application 1750 passes the authenticationdata it receives over the authentication virtual channel to its securityservice 1712′. If the server-side security service 1712′ is able toverify the data, it generates an access token representing a logonsession for the user, allowing the user to authenticate to the remotemachine 30 without resubmitting authentication credentials. An accesstoken is a data object that includes, among other things, a locallyunique identifier (LUID) for the logon session. If the server-sidesecurity service 1712′ is not able to verify the data, the user isprompted to resubmit authentication credentials.

In some embodiments, until the server-side security service 1712′authenticates the user, the only virtual channel over which the user maycommunicate with the remote machine 30 is the authentication virtualchannel. In some of these embodiments, after authentication, new virtualchannels are initiated for communication. In other embodiments, only onevirtual channel exists and it may only be used forauthentication-related communications until the user is authenticated,and it may be used for other communications after the user isauthenticated.

For embodiments in which the remote machine 30 operates under control ofa MICROSOFT WINDOWS operating system, the access token generated by theserver-side security service 1712′ is an impersonation token that hasonly network logon rights. That is, the generated access token is notsuitable to use for starting applications to run interactively, as isrequired in the WINDOWS server-based computing environment. To allowapplications to run interactively, a primary access token is needed thathas interactive logon rights. Inone embodiment, the generated accesstoken is modified to provide the appropriate rights. In anotherembodiment, a new token is generated for the user.

For embodiments in which the server-side computing device 140 operatesunder control of a Unix-based operating system, if the server-sidesecurity service 1712′ verifies the authentication data it receives overthe authentication virtual channel from the server-side thin-clientapplication 1750, the server-side thin-client application 1750 willgrant the user access to the resources. In these embodiments, theserver-side security service 1712′ does not generate an access token.

In some embodiments, after the remote machine 30 has authenticated theuser, the remote machine 30 presents an enumeration of resourcesavailable to the user. In these embodiments, the remote machine 30 maycreate a page describing a display of resources, hosted by a pluralityof machines, available to the machine 100. The remote machine 30 maythen transmit the created page to the machine 100 for display andreceive from the machine 100, a request to access one of the hostedresources.

In some of these embodiments, the selected one of the availableresources hosted by one of the plurality of machines is then executedwithout requiring further receipt of user authentication data from themachine 100. In some of these embodiments, the remote machine 30initiates, in response to successful authentication by the user, aconnection from the remote machine 30 to a second remote machine 30′which is hosting a resource available to the user. In these embodiments,the available resource is executed over the connection. In someembodiments, the connection is a virtual channel.

In other embodiments, the first remote machine 30 is hosting theselected one of the available resources. In some of these embodiments,the remote machine 30 makes the resource available to the user over theexisting connection. In others of these embodiments, the remote machine30 makes the resource available to the user over a new connection. Insome of those embodiments, the new connection comprises a virtualchannel.

In some embodiments, a plurality of components are provided forauthenticating a user of the client machine 10 to a virtual machine on aremote machine 30. In one of these embodiments, functionality isprovided for a Kerberos-based Single Sign-On process between the clientmachine 10 and a guest operating system provided by the virtual machine.

In some embodiments, a user seeking to access a resource provided by avirtual machine provides authentication credentials multiple times todifferent entities. In one of these embodiments, the user isauthenticated by a client agent on the client machine 10, by a remotemachine 30, and by a computing environment provided by a virtual machinein the remote machine 30. In some of these embodiments, single sign-onsupport would enable authentication of the user to different entitieswith only one transmission of authentication credentials from the user.

Authentication of the user to the client machine and the remote machine30 may be accomplished as described above in connection with FIG. 17. Insome embodiments, an authentication component, a GINA (GraphicalIdentification and Authentication) component, an authentication modulein the session management component and an authentication module for thevirtual machine service component are provided. In one embodiment, abidirectional virtual channel enables communication between a servicemanagement component on the remote machine 30 and a virtual machineservice component executing in the guest operating system. In oneembodiment, the remote machine 30 includes client-side single sign-onfunctionality and the virtual machine includes server-side singlesign-on functionality. In still another embodiment, the servicemanagement component implements an authentication module andcommunicates with an authentication module in the virtual machineservice component to authenticate the user.

In one embodiment, the session management component creates a KerberosSSPI channel between itself and the virtual machine service component.When the channel is established the session management componentacquires the credentials of the user and initializes a security contextusing this data. The initialization data returned is sent to the virtualmachine service component which accepts the data and starts an exchangeof SSPI messages between the two components until the security contextis established in the virtual machine service component. This context isthen used to log the user onto the virtual machine using a singlesign-on GINA component.

In some embodiments, the session management component authenticates theuser to a host operating system on the remote machine 30. In one ofthese embodiments, the host operating system then authenticates the userto the virtual machine. In other embodiments, the session managementcomponent authenticates the user to a hypervisor. In one of theseembodiments, the hypervisor then authenticates the user to the virtualmachine. In still other embodiments, the session management componentauthenticates the user to a virtual machine providing managementfunctionality for the virtual machine to which the user seeks access.

Referring back to FIG. 8, a remote machine 30 may determine to provideaccess to a resource streaming service capable of transmitting arequested resource to the client machine (step 816). In someembodiments, the remote machine 30 determines to implement a resourcestreaming service to transmit to the client machine 10 or to a remotemachine 30′ a requested resource. In other embodiments, the remotemachine 30 determines to use a resource streaming service to stream theresource to a computing environment provided by a virtual machine.Instill other embodiments, the resource is a computing environment andthe remote machine 30 determines to use a resource streaming techniqueto stream the computing environment to a virtual machine. In someembodiments, the plurality of resource files resides on the remotemachine 30′. In other embodiments, the plurality of resource filesresides on a separate file server or remote machine 30″. Instill otherembodiments, the plurality of resource files may be transmitted to aclient machine 10. In yet other embodiments, a file in the plurality ofresource files may be executed prior to transmission of a second file inthe plurality of resource files to the client machine 10.

In some embodiments, the remote machine 30 retrieves information aboutthe enumerated resource from a remote machine 30′. In one of theseembodiments, the remote machine 30 receives an identification of aremote machine 30″ hosting a plurality of resource files. In another ofthese embodiments, the remote machine 30 receives identification of alocation of a plurality of resource files, the identification conformingto a Universal Naming Convention (UNC). Instill another of theseembodiments, the identification includes a network location and a socketfor a resource streaming protocol.

In one embodiment, the remote machine 30 retrieves a file containinginformation about the enumerated resource. The file may include anidentification of a location of a remote machine 30′ hosting theenumerated resource. The file may include an identification of aplurality of versions of the enumerated resource. The file may includean enumeration of a plurality of resource files comprising theenumerated resource. The file may include an identification of acompressed file comprising a plurality of resources files comprising theenumerated resource. The file may include an identification ofpre-requisites to be satisfied by a machine executing the enumeratedresource. The file may include an enumeration of data files associatedwith the enumerated resource. The file may include an enumeration ofscripts to be executed on a machine executing the enumerated resource.The file may include an enumeration of registry data associated with theenumerated resource. The file may include an enumeration of rules foruse in an embodiment where the enumerated resource executes within anisolation environment. In one embodiment, the file may be referred to asa “manifest” file. The information that the file may contain isdescribed in further detail below.

The stream of data packets may include resource files comprising theenumerated resource. In some embodiments, resource files include datafiles associated with an resource. In other embodiments, resource filesinclude executable files required for execution of the resource. Instill other embodiments, the resource files include metadata includinginformation about the files, such as location, compatibilityrequirements, configuration data, registry data, identification ofexecution scripts rules for use in isolation environments, orauthorization requirements.

In some embodiments, the streamed resource executes prior to thetransmission of each resource file in a plurality of resource filescomprising the streamed resource. In one of these embodiments, executionof the streamed resource begins upon receipt by a client machine 10 ofone resource file in the plurality of resources. In another of theseembodiments, execution of the streamed resource begins upon receipt by aclient machine 10 of an executable resource file in the plurality ofresource files. In still another of these embodiments, the clientmachine 10 executes a first received resource file in a plurality ofresource files and the first received resource file requests access to asecond resource file in the plurality of resource files.

In one embodiment, the streamed resource executes on the client machine10 without permanently residing on the client machine 10. In thisembodiment, the streamed resource may execute on the client machine 10and be removed from the client machine 10 upon termination of thestreamed resource. In another embodiment, the streamed resource executeson the client machine 10 after a pre-deployed copy of each resource fileis stored on the client machine 10. In still another embodiment, thestreamed resource executes on the client machine 10 after a copy of eachresource file is stored in an isolation environment on the clientmachine 10. In yet another embodiment, the streamed resource executes onthe client machine 10 after a copy of each resource file is stored in acache on the client machine 10.

In some embodiments, the remote machine 30 streams the enumeratedresource to the remote machine 30, executes the enumerated resource onthe remote machine 30, and provides to the client machine 10resource-output data generated by the execution of the enumeratedresource. In other embodiments, a resource is streamed to a virtualmachine and resource output data is transmitted to a client machine 10using a presentation layer protocol such as X11, VNC, ICA or RDP.

In one embodiment, the remote machine 30 receives a plurality ofresource files comprising the enumerated resource. In anotherembodiment, the remote machine 30 provides the resource-output data viaa presentation level protocol, such as an ICA presentation levelprotocol or a Remote Desktop Windows presentation level protocol or anX-Windows presentation level protocol.

In some embodiments, the remote machine 30 also provides accessinformation associated with the enumerated resource, the accessinformation generated responsive to the selected method. In one of theseembodiments, the access information provides an indication to the clientmachine 10 of the selected method for execution of the enumeratedresource. In another of these embodiments, the access informationincludes an identification of a location of the enumerated resource, theidentification conforming to a Universal Naming Convention (UNC). Instill another of these embodiments, the access information includes anidentification of a session management server.

In some embodiments, the access information includes a launch ticketcomprising authentication information. In one of these embodiments, theclient machine 10 may use the launch ticket to authenticate the accessinformation received from the remote machine 30. In another of theseembodiments, the client machine 10 may use the launch ticket toauthenticate itself to a second remote machine 30 hosting the enumeratedresource. In still another of these embodiments, the remote machine 30includes the launch ticket in the access information responsive to arequest from the client machine 10 for the launch ticket.

Referring now to FIG. 18, flow diagram depicts one embodiment of thesteps taken to access a plurality of files comprising a resource, suchas a computing environment or an application program. A client machine10 performs a pre-launch analysis (step 1810). In one embodiment, theclient machine 10 performs the pre-launch analysis prior to retrievingand executing a plurality of resource files comprising a resource. Inanother embodiment, the client machine 10 performs the pre-launchanalysis responsive to a received indication that the pre-launchanalysis is a requirement for authorization to access the plurality ofresource files comprising a resource.

In some embodiments, the client machine 10 receives, from a remotemachine 30, access information associated with the plurality of resourcefiles. In one of these embodiments, the access information includes anidentification of a location of a remote machine 30′ hosting theplurality of resource files. In another of these embodiments, the clientmachine 10 receives an identification of a plurality of resourcescomprising one or more versions of the resource. In still another ofthese embodiments, the client machine 10 receives an identification of aplurality of resource files comprising one or more resources. In otherembodiments, the client machine 10 receives an enumeration of resourcesavailable to the client machine 10 for retrieval and execution. In oneof these embodiments, the enumeration results from an evaluation of theclient machine 10. In still other embodiments, the client machine 10retrieves at least one characteristic responsive to the retrievedidentification of the plurality of resource files comprising a resource.

In some embodiments, the access information includes a launch ticketcapable of authorizing the client machine 10 to access the plurality ofresource files. In one of these embodiments, the launch ticket isprovided to the client machine 10 responsive to an evaluation of theclient machine 10. In another of these embodiments, the launch ticket isprovided to the client machine 10 subsequent to a pre-launch analysis ofthe client machine 10 by the client machine 10.

In other embodiments, the client machine 10 retrieves at least onecharacteristic required for execution of the plurality of resourcefiles. In one of these embodiments, the access information includes theat least one characteristic. In another of these embodiments, the accessinformation indicates a location of a file for retrieval by the clientmachine 10, the file enumerating the at least one characteristic. Instill another of these embodiments, the file enumerating the at leastone characteristic further comprises an enumeration of the plurality ofresource files and an identification of a remote machine 30 hosting theplurality of resource files.

The client machine 10 determines the existence of the at least onecharacteristic on the client machine 10. In one embodiment, the clientmachine 10 makes this determination as part of the pre-launch analysis.In another embodiment, the client machine 10 determines whether theclient machine 10 has the at least one characteristic.

In one embodiment, determining the existence of the at least onecharacteristic on the client machine 10 includes determining whether adevice driver is installed on the client machine 10. In anotherembodiment, determining the existence of the at least one characteristicon the client machine 10 includes determining whether an operatingsystem is installed on the client machine 10. In still anotherembodiment, determining the existence of the at least one characteristicon the client machine 10 includes determining whether a particularoperating system is installed on the client machine 10. In yet anotherembodiment, determining the existence of the at least one characteristicon the client machine 10 includes determining whether a particularrevision level of an operating system is installed on the client machine10. For embodiments in which a remote machine 30 acts as a clientmachine 10 (such as, for example, a terminal services session in whichthe remote machine executes computing resources on behalf of a user of aclient machine), determining the existence of at least on characteristicmay include determining whether the remote machine 30 executes ahypervisor or, alternatively, whether the remote machine executes ahypervisor which itself executes in the native operating system.

In some embodiments, determining the existence of the at least onecharacteristic on the client machine 10 includes determining whether theclient machine 10 has acquired authorization to execute an enumeratedresource. In one of these embodiments, a determination is made by theclient machine 10 as to whether the client machine 10 has received alicense to execute the enumerated resource. In another of theseembodiments, a determination is made by the client machine 10 as towhether the client machine 10 has received a license to receive across aresource streaming session a plurality of resource files comprising theenumerated resource. In other embodiments, determining the existence ofthe at least one characteristic on the client machine 10 includesdetermining whether the client machine 10 has sufficient bandwidthavailable to retrieve and execute an enumerated resource.

In some embodiments, determining the existence of the at least onecharacteristic on the client machine 10 includes execution of a scripton the client machine 10. In other embodiments, determining theexistence of the at least one characteristic on the client machine 10includes installation of software on the client machine 10. In stillother embodiments, determining the existence of the at least onecharacteristic on the client machine 10 includes modification of aregistry on the client machine 10. In yet other embodiments, determiningthe existence of the at least one characteristic on the client machine10 includes transmission of a collection agent 704 to the client machine10 for execution on the client machine 10 to gather credentialsassociated with the client machine 10.

The client machine 10 requests, from a remote machine 30, authorizationfor execution of the plurality of resource files, the request includinga launch ticket (step 1812). In some embodiments, the client machine 10makes the request responsive to a determination that at least onecharacteristic exists on the client machine 10. In one of theseembodiments, the client machine 10 determines that a plurality ofcharacteristics exist on the client machine 10, the plurality ofcharacteristics associated with an enumerated resource and receivedresponsive to a request to execute the enumerated resource. In anotherof these embodiments, whether the client machine 10 receives anindication that authorization for execution of the enumerated resourcefiles depends upon existence of the at least one characteristic on theclient machine 10. In one embodiment, the client machine 10 received anenumeration of resources, requested execution of an enumerated resource,and received access information including the at least onecharacteristic and a launch ticket authorizing the execution of theenumerated resource upon the determination of the existence of the atleast one characteristic on the client machine 10. In one embodiment,the client machine 10 receives from the remote machine 30 a licenseauthorizing execution of the plurality of resource files. In someembodiments, the license authorizes execution for a specified timeperiod. In one of these embodiments, the license requires transmissionof a heart beat message to maintain authorization for execution of theplurality of resource files. For embodiments in which a virtual machineis streamed or otherwise downloaded to the client machine, a licensepool may be provided that authorizes the virtual machine, its guestoperating system and all the licensed software installed within thatguest operating system. In some of these embodiments, a single licenseis provided that authorizes those entities.

In another embodiment, the client machine 10 receives from the remotemachine 30 the license and an identifier associated with a remotemachine 30 monitoring execution of the plurality of resource files. Insome embodiments, the remote machine 30 is a session management server1962, as described below in connection with FIG. 19. In one of theseembodiments, the session management server 1962 includes a sessionmanagement subsystem 1910 that monitors the session associated with theclient machine 10. In other embodiments, a separate remote machine 30″″is the session management server 1962.

Referring back to FIG. 18, the client machine 10 receives and executesthe plurality of resource files (step 1814). In one embodiment, theclient machine 10 receives the plurality of resource files across aresource streaming session. In another embodiment, the client machine 10stores the plurality of resource files in an isolation environment onthe client machine 10. In still another embodiment, the client machine10 executes one of the plurality of resource files prior to receiving asecond of the plurality of resource files. In some embodiments, a remotemachine 30 transmits the plurality of resource files to a plurality ofclient machines 10, each client machine 10 in the plurality havingestablished a separate resource streaming session with the remotemachine 30.

In some embodiments, the client machine 10 stores the plurality ofresource files in a cache and delays execution of the resource files. Inone of these embodiments, the client machine 10 receives authorizationto execute the resource files during a pre-defined period of time. Inanother of these embodiments, the client machine 10 receivesauthorization to execute the resource files during the pre-definedperiod of time when the client machine 10 lacks access to a network. Inother embodiments, the client machine 10 stores the plurality ofresource files in a cache. In one of these embodiments, a resourcestreaming client 1952 (described in further detail below in connectionwith FIG. 19) establishes an internal resource streaming session toretrieve the plurality of resource files from the cache. In another ofthese embodiments, the client machine 10 receives authorization toexecute the resource files during a pre-defined period of time when theclient machine 10 lacks access to a network.

The client machine 10 transmits at least one heartbeat message to aremote machine (step 1816). In some embodiments, the client machine 10transmits the at least one heartbeat message to retain authorization toexecute the plurality of resource files comprising the enumeratedresource. In other embodiments, the client machine 10 transmits the atleast one heartbeat message to retain authorization retrieve a resourcefile in the plurality of resource files. In still other embodiments, theclient machine 10 receives a license authorizing execution of theplurality of resource files during a pre-determined period of time.

In some embodiments, the client machine 10 transmits the heartbeatmessage to a second remote machine 30″″. In one of these embodiments,the second remote machine 30″″ may comprise a session management server1962 monitoring the retrieval and execution of the plurality of resourcefiles. In another of these embodiments, the second remote machine 30″″may renew a license authorizing execution of the plurality of resourcefiles, responsive to the transmitted heartbeat message. In still anotherof these embodiments, the second remote machine 30″″ may transmit to theclient machine 10 a command, responsive to the transmitted heartbeatmessage.

Referring now to FIG. 19, the client machine 10 may include a resourcestreaming client 1952, a streaming service 1954 and an isolationenvironment 1956.

The resource streaming client 1952 may be an executable program. In someembodiments, the resource streaming client 1952 may be able to launchanother executable program. In other embodiments, the resource streamingclient 1952 may initiate the streaming service 1954. In one of theseembodiments, the resource streaming client 1952 may provide thestreaming service 1954 with a parameter associated with executing aresource. In another of these embodiments, the resource streaming client1952 may initiate the streaming service 1954 using a remote procedurecall.

In one embodiment, the client machine 10 requests execution of aresource and receives access information from a remote machine 30regarding execution. In another embodiment, the resource streamingclient 1952 receives the access information. In still anotherembodiment, the resource streaming client 1952 provides the accessinformation to the streaming service 1954. In yet another embodiment,the access information includes an identification of a location of afile associated with a plurality of resource files comprising theresource.

In one embodiment, the streaming service 1954 retrieves a fileassociated with a plurality of resource files. In some embodiments, theretrieved file includes an identification of a location of the pluralityof resource files. In one of these embodiments, the streaming service1954 retrieves the plurality of resource files. In another of theseembodiments, the streaming service 1954 executes the retrieved pluralityof resource files on the client machine 10. In other embodiments, thestreaming service 1954 transmits heartbeat messages to a remote machine30 to maintain authorization to retrieve and execute a plurality ofresource files.

In some embodiments, the retrieved file includes an identification of alocation of more than one plurality of resource files, each plurality ofresource files comprising a different resource. In one of theseembodiments, the streaming service 1954 retrieves the plurality ofresource files comprising the resource compatible with the clientmachine 10. In another of these embodiments, the streaming service 1954receives authorization to retrieve a particular plurality of resourcefiles, responsive to an evaluation of the client machine 10.

In some embodiments, the plurality of resource files are compressed andstored on a file server within an archive file such as a CAB, ZIP, SIT,TAR, JAR or other archive file. In one embodiment, a plurality ofresource files stored in an archive file comprises a resource. Inanother embodiment, multiple pluralities of resource files stored in anarchive file each comprise different versions of a resource. In stillanother embodiment, multiple pluralities of resource files stored in anarchive file each comprise different resources. In some embodiments, anarchive file includes metadata associated with each file in theplurality of resource files. In one of these embodiments, the streamingservice 1954 generates a directory structure responsive to the includedmetadata. As will be described in greater detail below, the metadata maybe used to satisfy requests by resources for directory enumeration.

In one embodiment, the streaming service 1954 decompresses an archivefile to acquire the plurality of resource files. In another embodiment,the streaming service 1954 determines whether a local copy of a filewithin the plurality of resource files exists in a cache on the clientmachine 10 prior to retrieving the file from the plurality of resourcefiles. In still another embodiment, the file system filter driver 1964determines whether the local copy exists in the cache. In someembodiments, the streaming service 1954 modifies a registry entry priorto retrieving a file within the plurality of resource files.

In some embodiments, the streaming service 1954 stores a plurality ofresource files in a cache on the client machine 10. In one of theseembodiments, the streaming service 1954 may provide functionality forcaching a plurality of resource files upon receiving a request to cachethe plurality of resource files. In another of these embodiments, thestreaming service 1954 may provide functionality for securing a cache onthe client machine 10. In another of these embodiments, the streamingservice 1954 may use an algorithm to adjust a size and a location of thecache.

In some embodiments, the streaming service 1954 creates an isolationenvironment 1956 on the client machine 10. In one of these embodiments,the streaming service 1954 uses an isolation environment applicationprogramming interface to create the isolation environment 1956. Inanother of these embodiments, the streaming service 1954 stores theplurality of resource files in the isolation environment 1956. In stillanother of these embodiments, the streaming service 1954 executes a filein the plurality of resource files within the isolation environment. Inyet another of these embodiments, the streaming service 1954 executesthe resource in the isolation environment. In some embodiments, thestreaming service 1954 accesses an isolation environment 1956 providedby a virtual machine.

For embodiments in which authorization is received to execute a resourceon the client machine 10, the execution of the resource may occur withinan isolation environment 1956. In some embodiments, a plurality ofresource files comprising the resource is stored on the client machine10 prior to execution of the resource. In other embodiments, a subset ofthe plurality of resource files is stored on the client machine 10 priorto execution of the resource. In still other embodiments, the pluralityof resource files does not reside in the isolation environment 1956. Inyet other embodiments, a subset of the plurality of resources files donot reside on the client machine 10. Regardless of whether a subset ofthe plurality of resource files or each resource file in the pluralityof resource files reside on the client machine 10 or in isolationenvironment 1956, in some embodiments, a resource file in the pluralityof resource files may be executed within an isolation environment 1956.

In some embodiments, isolation environments are used to provideadditional functionality to the resource streaming client 1952. In oneof these embodiments, a resource is executed within an isolationenvironment. In another of these embodiments, a retrieved plurality ofresource files resides within the isolation environment. In stillanother of these embodiments, changes to a registry on the clientmachine 10 are made within the isolation environment.

In one embodiment, the resource streaming client 1952 includes anisolation environment 1956. In some embodiments, the resource streamingclient 1952 includes a file system filter driver 1964 interceptingresource requests for files. In one of these embodiments, the filesystem filter driver 1964 intercepts a resource request to open anexisting file and determines that the file does not reside in theisolation environment 1956. In another of these embodiments, the filesystem filter driver 1964 redirects the request to the streaming service1954 responsive to a determination that the file does not reside in theisolation environment 1956. The streaming service 1954 may extract thefile from the plurality of resource files and store the file in theisolation environment 1956. The file system filter driver 1964 may thenrespond to the request for the file with the stored copy of the file. Insome embodiments, the file system filter driver 1964 may redirect therequest for the file to a file server 1940, responsive to an indicationthat the streaming service 1954 has not retrieved the file or theplurality of resource files and a determination the file does not residein the isolation environment 1956.

In some embodiments, the file system filter driver 1964 uses a strictisolation rule to prevent conflicting or inconsistent data fromappearing in the isolation environment 1956. In one of theseembodiments, the file system filter driver 1964 intercepting a requestfor a resource in a user isolation environment may redirect the requestto a resource isolation environment. In another of these embodiments,the file system filter driver 1964 does not redirect the request to asystem scope.

In one embodiment, the streaming service 1954 uses IOCTL commands tocommunicate with the filter driver. In another embodiment,communications to the file server 1940 are received with the MicrosoftSMB streaming protocol.

Referring now to FIG. 20, a flow diagram depicts one embodiment of stepstaken by a client machine 10 to execute a resource. As described abovein FIG. 18, regarding step 1814, a client machine 10 receives andexecutes the plurality of resource files. In brief overview, the clientmachine 10 receives a file including access information for accessing aplurality of resource files and for executing a first client capable ofreceiving a resource stream (step 2002). The client machine 10 retrievesan identification of the plurality of resource files, responsive to thefile (step 2004). The client machine 10 retrieves at least onecharacteristic required for execution of the plurality of resourcefiles, responsive to the file (step 2006). The client machine 10determines whether the client machine 10 includes the at least onecharacteristic (step 2008). The client machine 10 executes a secondclient, the second client requesting execution of the plurality ofresource files on a remote machine 30, responsive to a determinationthat the client machine 10 lacks the at least one characteristic (step2010).

Referring to FIG. 20, and in greater detail, the client machine 10receives a file including access information for accessing a pluralityof resource files and for executing a first client capable of receivinga resource stream (step 2002). In one embodiment, the client machine 10receives access information including an identification of a location ofa plurality of resource files comprising a resource. In anotherembodiment, the client machine 10 receives the file responsive torequesting execution of the resource. In still another embodiment, theaccess information includes an indication that the plurality of resourcefiles reside on a remote machine 30′ such as a resource server or a fileserver. In yet another embodiment, the access information indicates thatthe client machine 10 may retrieve the plurality of resource files fromthe remote machine 30 over a resource streaming session.

The client machine 10 retrieves an identification of the plurality ofresource files, responsive to the file (step 2004). In one embodiment,the client machine 10 identifies a remote machine 30 on which theplurality of resource files resides, responsive to the file includingaccess information. In another embodiment, the client machine 10retrieves from the remote machine 30 a file identifying the plurality ofresource files. In some embodiments, the plurality of resource filescomprises a resource. In other embodiments, the plurality of resourcefiles comprises multiple resources. In still other embodiments, theplurality of resource files comprises multiple versions of a singleresource.

Referring ahead to FIG. 21, a block diagram depicts one embodiment of aplurality of resource files residing on a remote machine 30′, such asfile server 1940. In FIG. 21, a plurality of resource files, referred toas a package, includes resource files comprising three differentversions of one or more resources.

In one embodiment, each subset of resource files comprising a version ofone or more resources and stored within the package is referred to as atarget. Target 1, for example, includes a version of a word processingresource and of a spreadsheet program, the version compatible with theEnglish language version of the Microsoft Windows 2000 operating system.Target 2 includes a version of a word processing resource and of aspreadsheet program, the version compatible with the English languageversion of the Microsoft XP operating system. Target 3 a version of aword processing resource and of a spreadsheet program, the versioncompatible with the Japanese language version of the Microsoft Windows2003 operating system with service pack 3.

Returning back to FIG. 20, in some embodiments, the file retrieved fromthe remote machine 30 hosting the plurality of resource files includes adescription of the package and the targets included in the plurality ofresource files. In other embodiments, the file retrieved from the remotemachine 30 identifies the plurality of resource files comprising aresource requested for execution by the client machine 10.

The client machine 10 retrieves at least one characteristic required forexecution of the plurality of resource files, responsive to the file(step 2006). In some embodiments, the client machine 10 may not executea resource unless the client machine 10 includes certaincharacteristics. In one of these embodiments, different resourcesrequire client machines 10 to include different characteristics from thecharacteristics required by other resources. In another of theseembodiments, the client machine 10 receives an identification of the atleast one characteristic required for execution of the plurality ofresource files comprising the resource requested by the client machine10.

Still referring to FIG. 20, the client machine 10 determines whether theclient machine 10 includes the at least one characteristic (step 2008).In one embodiment, the client machine 10 evaluates an operating systemon the client machine 10 to determine whether the client machine 10includes the at least one characteristic. In another embodiment, theclient machine 10 identifies a language used by an operating system onthe client machine 10 to determine whether the client machine 10includes the at least one characteristic. In still another embodiment,the client machine 10 identifies a revision level of an operating systemon the client machine 10 to determine whether the client machine 10includes the at least one characteristic. In yet another embodiment, theclient machine 10 identifies a resource version of a resource residingon the client machine 10 to determine whether the client machine 10includes the at least one characteristic. In some embodiments, theclient machine 10 determines whether the client machine 10 includes adevice driver to determine whether the client machine 10 includes the atleast one characteristic. In other embodiments, the client machine 10determines whether the client machine 10 includes an operating system todetermine whether the client machine 10 includes the at least onecharacteristic. In still other embodiments, the client machine 10determines whether the client machine 10 includes a license to executethe plurality of resource files to determine whether the client machine10 includes the at least one characteristic.

In one embodiment, the client machine 10 determines whether the clientmachine 10 comprises a required amount of available disk space to accessthe resource. In another embodiment, the client machine 10 determineswhether a central processing unit of the client machine 10 provides arequired processing speed. In still another embodiment, the clientmachine 10 determines whether the client machine 10 comprises a requiredamount of available RAM. In yet another embodiment, the client machine10 determines whether the client machine 10 comprises a required levelof graphical processing and display capabilities.

The client machine 10 executes a second client, the second clientrequesting execution of the plurality of resource files on a remotemachine 30, responsive to a determination that the client machine 10lacks the at least one characteristic (step 2010). In one embodiment,when the client machine 10 determines that the client machine 10 lacksthe at least one characteristic, the client machine 10 does not executethe first client capable of receiving a resource stream. In anotherembodiment, a policy prohibits the client machine 10 from receiving theplurality of resource files over a resource stream when the clientmachine 10 lacks the at least one characteristic. In some embodiments,the client machine 10 determines that the client machine 10 does includethe at least one characteristic. In one of these embodiments, the clientmachine 10 executes the first client, the first client receiving aresource stream comprising the plurality of resource files from a remotemachine 30 for execution on the client machine 10.

In some embodiments, the client machine 10 executes the second clientrequesting execution of the plurality of resource files on a remotemachine 30 upon determining that the client machine 10 lacks the atleast one characteristic. In one of these embodiments, the second clienttransmits the request to a remote machine 30 hosting the plurality ofresource files. In another of these embodiments, the remote machine 30executes the plurality of resource files comprising the resource andgenerates resource-output data. In still another of these embodiments,the second client receives resource-output data generated by executionof the plurality of resource files on the remote machine 30. In yetanother of these embodiments, the second client displays theresource-output on the client machine 10. In one embodiment, the clientmachine 10 requests execution of the plurality of application files on aphysical machine 30. In another embodiment, the client machine 10requests execution of the plurality of application files on a virtualmachine executing on a remote machine 30.

In some embodiments, the second client receives a file comprising accessinformation for accessing a plurality of resource files and requests,responsive to a determination by the first client that the clientmachine 10 lacks the at least one characteristic, execution of theplurality of resource files on a virtual machine providing a computingenvironment having the least one characteristic. In other embodiments,the client machine 10 executes the second client requesting execution ofthe plurality of resource files on a remote machine 30 upon determiningthat the client machine 10 lacks the at least one characteristic. In oneof these embodiments, the second client transmits the request to aremote machine 30 hosting the plurality of resource files. In another ofthese embodiments, a virtual machine executing on the remote machine 30executes the plurality of resource files comprising the resource andgenerates resource-output data. In still another of these embodiments,the second client receives resource-output data generated by executionof the plurality of resource files on the virtual machine. In yetanother of these embodiments, the second client displays theresource-output on the client machine 10.

In some embodiments, the second client transmits the request to a remotemachine 30 that does not host the plurality of resource files. In one ofthese embodiments, the remote machine 30 may request the plurality ofresource files from a second remote machine 30 hosting the plurality ofresource files. In another of these embodiments, the remote machine 30may receive the plurality of resource files from the second remotemachine 30 across a resource streaming session. In still another ofthese embodiments, the remote machine 30 stores the received pluralityof resource files in an isolation environment and executes the resourcewithin the isolation environment. In yet another of these embodiments,the remote machine 30 transmits the generated resource-output data tothe second client on the client machine 10.

In some embodiments, the second client transmits the request to a remotemachine 30 that does not host the plurality of resource files. In one ofthese embodiments, the remote machine 30 may request the plurality ofresource files from a second remote machine 30 hosting the plurality ofresource files. In another of these embodiments, the remote machine 30may receive the plurality of resource files from the second remotemachine 30 across a resource streaming session.

In other embodiments, the remote machine 30 stores the receivedplurality of resource files in a computing environment provided by avirtual machine executing on the remote machine 30, the computingenvironment having the at least one characteristic. In yet another ofthese embodiments, the remote machine 30 executes the resource withinthe computing environment provided by the virtual machine and transmitsthe generated resource-output data to the second client on the clientmachine 10.

In some embodiments, a virtual machine on the remote machine 30 executesthe plurality of resource files. In one of these embodiments, thevirtual machine receives for execution a resource stream comprising theplurality of resource files. In some embodiments, a virtual machine mayreceive for execution a resource stream responsive to an application ofa policy. In one of these embodiments, the result of the application ofthe policy depends on an availability of the requested resource in themachine farm 38 (including availability of a suitably configuredphysical machine 30 or virtual machine), the sensitivity of therequested resource (including whether a policy prevents the transmissionof the requested resource to an unsecured environment), informationassociated with the user of the client machine 10 (includingauthorization to execute or access the requested resource in anunsecured environment).

Referring back to FIG. 19, in one embodiment, the first client machine10, capable of receiving the resource stream, is a resource streamingclient 1952. The resource streaming client 1952 receiving the file,retrieving an identification of a plurality of resource files and atleast one characteristic required for execution of the plurality ofresource files, responsive to the file, and determining whether theclient machine 10 includes the at least one characteristic. In anotherembodiment, the second client is a client agent 1960. In someembodiments, the client agent 1960 receives the file from the resourcestreaming client 1952 responsive to a determination, by the resourcestreaming client 1952, that the client machine 10 lacks the at least onecharacteristic.

A remote machine 30 includes functionality for monitoring resource usageby a client machine 10. The remote machine 30 may monitor the status ofeach resource used by the client machine 10, for example upon executionor termination of a resource. In one embodiment, the remote machine 30requires the client machine 10 to transmit messages about the status ofa resource executed by the client machine 10. In another embodiment,when a client machine 10 connects to a network on which the remotemachine 30 resides, the client machine 10 transmits a message indicatingthat the client machine 10 has connected to the network.

In one embodiment, the client machine 10 is said to have a session whenthe client machine 10 interacts with the remote machine 30 and executesone or more resources. In another embodiment, the remote machine 30requires the client machine 10 to maintain, for the duration of asession, a license authorizing execution of resources received from aremote machine 30. In still another embodiment, sessions have uniquesession identifiers assigned by the remote machine 30.

In one embodiment, the client machine 10 transmits the messages to theremote machine 30 with which it interacted to receive and execute theresource. In another embodiment, the client machine 10 receives from theremote machine 30 an identifier of a second remote machine 30, such as asession management server 1962, the second remote machine 30 receivingand storing all transmitted messages associated with the session on theclient machine 10.

In some embodiments, the session management server 1962 is a remotemachine 30 providing license management and session monitoring services.In one of these embodiments, the session management server 1962 includesa server management subsystem 1908 providing these services.

In one embodiment, the client machine 10 transmits messages directly tothe session management server 1962. In another embodiment, the clientmachine 10 transmits messages to a remote machine 30, the remote machine30 forwarding the messages to the session management server 1962 with anidentification of the client machine 10.

A client machine 10 may transmit a heartbeat message to the remotemachine 30. In one embodiment, the heartbeat message includes a requestfor a license. In this embodiment, the client machine 10 may transmitthe heartbeat message after receiving access information associated witha resource which the client machine 10 requested authorization toexecute. The client machine 10 may transmit the heartbeat message priorto executing the resource. In one embodiment, the client machine 10includes with the heartbeat message a launch ticket received with theaccess information. In this embodiment, the remote machine 30 may grantthe client machine 10 a license upon successful verification of thelaunch ticket.

In another embodiment, the heartbeat message includes an indication thatthe client machine 10 has initiated execution of a resource. In stillanother embodiment, the heartbeat message includes an indication thatthe client machine 10 has terminated execution of a resource. In yetanother embodiment, the heartbeat message includes an indication of afailure to execute a resource.

In one embodiment, the heartbeat message includes a request for anidentification of a second session management server, such as a sessionmanagement server 1962. In another embodiment, the heartbeat messageincludes an indication that the client machine 10 has connected to anetwork on which the remote machine 30 resides.

In some embodiments, the heartbeat message includes a request to reset aresource streaming session. In one of these embodiments, the clientmachine 10 transmits this heartbeat message when an error has occurredand a connection is terminated between a network on which the remotemachine 30 resides and the client machine 10. In another of theseembodiments, the client machine 10 transmits with the heartbeat messageinformation associated with the session. In still another of theseembodiments, the remote machine 30 may transmit to the client machine 10session-related data if the session has not expired.

In another of these embodiments, if a remote machine 30 disconnects froma network on which it replies, the client machine 10 may not receive areply to a heartbeat message transmitted to the remote machine 30. Inone embodiment, the client machine 10 may re-establish a session bytransmitting a message requesting a session reset to the remote machine30. In another embodiment, the client machine 10 may re-establish asession by transmitting a message requesting a session reset to a secondremote machine 30. In some embodiments, when the remote machine 30reconnects to the network, it will create anew session for each sessionreset request received while the remote machine 30 was disconnected. Inone of these embodiments, the new session will be associated with thereconnected and unlicensed state. In another of these embodiments,no newlicense will be acquired for the new session. In still another of theseembodiments, when the client machine 10 executes a resource, anewlicense will be acquired and all sessions associated with the clientmachine 10 will be associated with an active and licensed state.

In some embodiments, a resource streaming client 1952 on the clientmachine 10 generates the heartbeat message. In one of these embodiments,the resource streaming client 1952 forwards the heartbeat message to aweb interface 1958 for transmission to the client machine 10 fortransmission to the remote machine 30. In other embodiments, themanagement service 1904 on the remote machine 30 receives the heartbeatmessage from the client machine 10 via the web interface 1958. In stillother embodiments, a remote machine 30 comprising a collector point 240(described above) receives and stores the heartbeat messages.

In some embodiments, the resource streaming client 1952 requests alicense from the remote machine 30. In one of these embodiments, thelicense authorizes execution of a resource on the client machine 10. Inanother of these embodiments, the remote machine 30 may access a secondremote machine 30 to provide the license. In still another of theseembodiments, the remote machine 30 may provide the license to the clientmachine 10. In yet another of these embodiments, the remote machine 30may provide a license acceptable for authorization purposes to a secondremote machine 30. In some embodiments, the license is revoked upontermination of execution of a resource.

Referring back to FIG. 8, a request for access to a resource is received(step 802). In some embodiments, the resource is a file. In one of theseembodiments, an application program is selected and executed to provideaccess to the file. In another of these embodiments, a type of fileassociated with the requested file is identified to select anapplication program for execution. In still another of theseembodiments, prior to the request for access to the file, an applicationprogram is associated with a type of file, enabling automatic selectionof the application program upon identification of a type of fileassociated with the requested file. In some embodiments, file typeassociation (FTA) functionality permits users to automatically initiatethe execution of application programs associated with a data file, eventhough the data file and the executable program are hosted on differentcomputing nodes.

Typically, file type association functionality permits users totransparently execute executable programs by selecting data fileslocated on a computing machine that differs from the machine(s) wherethe executable programs are located. In one embodiment, a user of aclient machine 10 can transparently invoke the execution of anexecutable program on a remote machine 30 by selecting a data filelocated on the client machine 10. In another embodiment, a user cantransparently invoke the execution of an application program on theirclient machine 10 by selecting a data file located on a remote machine30. In still another embodiment, a user can select a data file stored ona remote machine 30′, such as a web server, and transparently invoke theexecution of an associated executable program on a remote machine 30,such as an application execution server. Typically, execution permitsprocessing of the contents of the selected data file, the output ofwhich is then provided to the user at the client machine 10.

It is to be understood that examples using filename extensionsnecessarily reflect the idiosyncrasies of embodiments utilizing theWINDOWS family of operating systems. Other embodiments implement methodsand apparatus in accord using special parameters stored in the data fileitself, the data contained in the data file, the file system recordsassociated with the data file, or a separate data file or database. Forexample, embodiments using the MacOS family of operating systems utilizefile and application creator types and store file-type association datain the Desktop file associated with each storage device. Embodimentsusing a UNIX-variant operating system utilize file extensions, embeddedparameters, or other mechanisms as appropriate. Accordingly, the scopeof the claims should not be read to be limited to embodiments relying onfilename extensions or embodiments utilizing WINDOWS operating systems.

Client-Based FTA

Referring to FIG. 22A, a flow diagram depicts one embodiment of thesteps taken in a method of enabling transparent distributed programexecution on a remote machine 30 through the selection of graphicalindicia representative of a data file located on the client machine 10.The client machine 10 receives, from one of a plurality of remotemachines 30, a mapping specifying an association between a type of datafile and an executable program for execution on one of a plurality ofremote machines 30 (Step 2206). In some embodiments, the mappingspecifies an association between a type of data file and an executableprogram for execution on a virtual machine located on one of a pluralityof remote machines 30.

The client machine 10 presents a graphical depiction of a data filestored on the client machine 10 (Step 2214) and receives a selection ofthe graphical depiction of the data file (Step 2218). The client machine10 identifies an executable program associated with the type of theselected data file using the received mapping (Step 2222) and sends arequest to a remote machine 30 for execution of the identifiedexecutable program (Step 2226). In one embodiment, the client machine 10initiates the execution of a local display application (Step 2230) toreceive application output data from the executing program (Step 2234),which it displays to the end user (Step 2238).

Still referring to FIG. 22A, when the client, machine 10 receives themapping (Step 106), the mapping may be received by itself, with severalother mappings, or with other messages or data such as software updates.Table 3 illustrates an exemplary mapping provided in one embodiment ofthe invention: TABLE 3 File type: Executable program: “.DOC”, “.RTF”MSWORD.EXE “.PDF” ACROBAT.EXE

In one embodiment, the mapping identifies an association between aparticular executable program for use with a particular data file ortype of data file stored on the user's client machine 10. In anotherembodiment, the mapping specifies the relationship between an executableprogram and a data file in terms of a client machine 10 application thatlaunches the executable program on a remote machine 30 and displays theoutput from execution at the client machine 10. For example, asdescribed in connection with FIG. 8A (step 2206), the mapping couldspecify that when a “.DOC” file is selected, the client machine 10 is toexecute METAFRAME from Citrix Software of Ft. Lauderdale, Fla., which inturn sends a request to one of a plurality of remote machines 30 toexecute WORD, receiving the output data from execution for display tothe user at the client machine 10. In some embodiments, a remote machine30 receiving the request to execute the application program chooses amethod for providing access to the application program, as describedabove in connection with FIG. 8 (step 804). In one of these embodiments,the remote machine 30 determines to execute the application and providethe application output data to the client machine 10. In another ofthese embodiments, the remote machine 30 identifies a remote machine 30that executes the application and provides the application output datato the client machine 10. In still another of these embodiments, theremote machine 30 identifies an application streaming service thattransmits the application program to the client machine 10 for localexecution. In yet another of these embodiments, the remote machine 30identifies a remote machine 30′ on which a virtual machine provides acomputing environment capable of executing the application program andtransmitting the application output data to the client machine 10.

In still another embodiment, mapping specifies the relationship betweenan executable program and a data file in terms of a client machine 10application that requests transmission of the executable program to theclient machine 10 from an application streaming service provided by aremote machine 30. In other embodiments, the mapping could specify thatwhen a file is selected, the client machine 10 is to establish aconnection to a virtual machine provided by one of a plurality of remotemachines 30 to initiate execution of an application program on thevirtual machine and to receive application output data from theexecution for display to the user at client machine 10. In some of theseembodiments, as described in connection with FIG. 8 (step 808), avirtual machine and an execution machine onto which the virtual machineis launched are identified, configured, and provide the user of theclient machine 10 with access to the file.

In some embodiments, the client machine 10 displays a list of filenamesassociated with data files stored on the client machine 10. In stillanother embodiment, indicia representative of files stored on the clientmachine 10 are intermingled with indicia representative of files storedon one or more remote machines 30, or on virtual machines executing onremote machines 30. In this embodiment, client-based FTA is operativewhen indicia representative of a file stored on the client machine 10 isselected. In another embodiment, multiple forms of FTA (see below) areoperative, with the appropriate form of FTA activated based on thelocation of the file associated with the selected indicia.

FIG. 22B illustrates one embodiment of the steps taken by a remotemachine 30 in the client-based file-type association process. A mappingis provided specifying an association between a type of data file storedon a client machine 10 and an executable program for execution on one ofa plurality of remote machines 30 (Step 2254). A request to execute theexecutable program is received (Step 2262) and the executable program isexecuted on one of a plurality of remote machines 30 (Step 2266). In oneembodiment, the remote machine 30 receiving the request to execute theexecutable program chooses to provide the requested access as describeabove in connection with FIG. 8 (step 2204 and step 2206). In someembodiments, the remote machine 30 receives a request for transmissionof the identified executable program to the client machine 10 for localexecution. In one of these embodiments, the remote machine 30 chooses toprovide the client machine 10 with the executable program via anapplication streaming service as described above. In another of theseembodiments, the remote machine 30 chooses to stream the executableprogram to a remote machine 30 or to a virtual machine executing on aremote machine 30′.

Server-Based FTA

Referring now to FIG. 23, a flow diagram depicts another embodiment ofthe steps taken in a method for enabling transparent distributed programexecution on a client machine 10 through the selection of graphicalindicia representative of a data file located on a remote machine 30.The client machine 10 presents a graphical depiction of a data filestored on one of a plurality of remote machines 30 (Step 2300). Theclient machine 10 receives a selection of the graphical depiction of thedata file (Step 2304) and transmits the selection to one of theplurality of remote machines 30 (Step 2308). The client machine 10receives a request from one of the plurality of remote machines 30 toexecute an executable program associated with the selected data file(Step 2312) and executes the associated executable program (Step 2316).

Still referring to FIG. 23, the client machine 10 presents a user with agraphical depiction of at least one data file stored on at least oneremote machine 30 (Step 2300). In one embodiment, indicia representativeof files stored on one or more remote machines 30, and on virtualmachines executing on the one or more remote machines 30, areintermingled with indicia representative of files stored on the clientmachine 10. In this embodiment, server-based FTA is operative whenindicia representative of a file stored on a remote machine 30 isselected. In another embodiment, multiple forms of FTA (see above,below) are operative, with the appropriate form of FTA activated basedon the location of the file associated with the selected graphicalindicia.

As described above in connection with FIG. 8 (step 804), a remotemachine 30 receiving a request to access a selected data file chooses amethod for providing access to the data file. In one embodiment, thedata file resides on the remote machine 30. In another embodiment, thedata file resides on a remote machine 30′, such as a web server. In someembodiments, the remote machine 30 consults a mapping to identify anapplication program associated with the requested data file.

In some embodiments, the remote machine 30 chooses to provide the clientmachine 10 with access to the file via execution of the associatedapplication program in a computing environment provided by a virtualmachine (step 806). In one of these embodiments, the remote machine 30may identify a remote machine 30′ to execute the application program andtransmit application output data to the client machine 10. In another ofthese embodiments, the remote machine 30 identifies a remote machine 30′to execute the application program in a computing environment providedby a virtual machine executing on the remote machine 30′, as describedin connection with FIG. 8 (step 808).

In other embodiments, the remote machine 30 identifies a remote machine30′ providing an application streaming service capable of transmittingthe application program to the client machine 10 for execution on theclient machine 10 as described in connection with FIG. 8 (step 816). Inone of these embodiments, the application streaming service transmitsthe application program to a remote machine 30′ for execution and theremote machine 30 transmits application output data resulting from theexecution to the client machine 10.

In some embodiments, the remote machine 30 selects one of apredetermined number of methods for executing a requested applicationprogram, responsive to a policy, the predetermined number of methodsincluding a method for executing the requested application in acomputing environment provided by a virtual machine. In one of theseembodiments, the application streaming service transmits the applicationprogram to a remote machine 30′ for executing in a computing environmentprovided by a virtual machine executing in the remote machine 30′. Inanother of these embodiments, the remote machine 30 selects a method forstreaming the requested application program to a virtual machine andexecuting the enumerated application in the virtual machine environment.In still another of these embodiments, the virtual machine is evaluatedand, a determination to stream the requested application is maderesponsive to the evaluation. In other embodiments, the determination tostream one of a plurality of files comprising an enumerated applicationprogram to a virtual machine is made responsive to credentials gatheredfrom a client machine 10.

Having received data associated with the selected data file, the clientmachine 10 typically processes the received data using the executingprogram and displays the result of the processing to the end user.

As described above, a client machine 10 connects to one or more of theremote machines 30 in the machine farm 38. In some of these embodiments,the client machine 10 may communicate with remote machines 30 to receiveapplication-output data generated by an execution of an applicationprogram on a remote machine 30, or on a virtual machine executing on theremote machine 30. In some embodiments, protocol stacks are implementedto enable communications between the client machine 10 and remotemachines 30.

FIG. 24 is a flow diagram depicting one particular embodiment of amethod for establishing an extensible and dynamically bindable protocolstack 20. In one embodiment, the method allows a client machine 10 tospecify the contents of a protocol stack dynamically without requiringthat a remote machine 30 have a prior protocol stack description for aparticular client machine and a particular application requirement.

In one embodiment, a remote machine 30 is on-line and monitoringactivity on a specific transport system (e.g. LAN or WAN) and hasinitialized its protocol stack with the minimal necessary protocolmodules to support a “TTY” communication mode. This mode is a raw ASCIIstream mode with no protocol assumptions above the transport layer (i.e.there are no protocol layers for compression, encryption, reliability,framing, or modem). Similarly, a client machine 10 seeking access to theremote machine 30 establishes a connection to the common transportsystem with the minimum protocol set needed to support a TTYcommunication mode.

Upon detecting that a client machine 10 has established transport systemconnection (step 2401), the application server broadcasts a TTY datastream,“DETECT.sub.--STRING”, in step 2402 that indicates service isavailable. The method used for detecting a client machine connection istransport system dependent (e.g. in the case of the TCP transport, whena client machine connects to a known port). If the client machine 10does not respond within a prescribed time period, step 2403 , are-broadcast of mission of the message occurs in step 2402 . Otherwisethe process proceeds to step 2405 where the client machine 10 sends theTTY string “DETECT-STRING”. In step 2406 , the client machine 10 waitsfor the remote machine 30 to respond and, if the response is within aprescribed time interval, the process proceeds to steps 2407 where theclient machine 10 enables the required protocol for supporting itsapplication. Otherwise, the client machine 10 repeats the transmissionof the message in step 2405 . The server responds in step 4108 byenabling the required set of protocols. At step 2409 , the TTY mode ofcommunication ends because the next message sent by the server is apresentation layer protocol packet, “PACKET.sub.--INIT.sub.--REQUEST”,which indicates that the client's required “DETECT.sub.--STRING” hasbeen received and accepted. In response to step 2409 , the client, atstep 2410 , sends a set of presentation layer protocol packets,“PACKET.sub.--INIT.sub.--RESPONSE”, each of which is used to specify arequired or optional protocol module that is being negotiated with theserver. At step 2411 , the server sends a set of“PACKET.sub.--INIT.sub.--CONNECT” packets. The number of packets isvariable: one for each client packet sent in step 2410 , thus giving theremote machine 30 the opportunity to negotiate the parameters underwhich communications will take place by overriding the parameters of theclient machine 10; or, the remote machine 30 may indicate that all ofthe parameters of the client machine 10 are acceptable by sending theparameters unchanged. At step 2412 the remote machine 30 enables thenegotiated protocols (including any optional protocols) of step 2411 .After the client machine 10 receives the packets from step 2411 , theclient machine 10 enables the negotiated protocols in step 2413 .

Still referring to FIG. 24, in some embodiments, a virtual machine hostserver communicates with the client machine 10 to enable negotiatedprotocols. As described above, a request is received from a clientmachine 10 for access to a computing environment or for applicationexecution, the request including an identification of a user of theclient machine 10 . In some embodiments, a virtual machine is launchedin communication with a hypervisor. In other embodiments, a virtualmachine host server is initialized with a prescribed set of protocolsand associated protocol parameters providing a common transportmechanism, wherein the common transport mechanism is for raw ASCIIstream mode communications. In still other embodiments, a virtualmachine host server is initialized with a prescribed set of protocolsand associated protocol parameters providing a common transportmechanism.

A virtual machine host server creates a first portion of a protocolstack. In one embodiment, a hypervisor creates the first portion of theprotocol stack. In another embodiment, the hypervisor transmits arequest protocol message to the client machine 10. In still anotherembodiment, the hypervisor receives from the client machine 10 aplurality of protocol packets specifying one or more protocol parametersdesired by the client machine 10. In yet another embodiment, the virtualmachine host server generates, in response to each received protocolpacket, a packet counter-specifying one or more protocol parameters.

The virtual machine host server transmits a request protocol message tothe client machine 10. The virtual machine host server receives from theclient machine 10 a plurality of protocol packets specifying one or moreprotocol parameters desired by the client machine 10. The virtualmachine host server transmits, in response to each received protocolpacket, a packet counter-specifying one or more protocol parameters. Inone embodiment, the virtual machine host server sends an acknowledgmentmessage to the client machine 10 indicating that at least one of theprotocols specified by the client machine 10 has been enabled. Inanother embodiment, the virtual machine host server responds to eachreceived protocol packet transmitted by the client machine 10 with avirtual machine host server protocol packet, at least one of the virtualmachine host server protocol packets modifying at least one of theassociated protocol parameters. The virtual machine host server createson the virtual machine host server a second portion of a protocol stack,the first portion and the second portion of the protocol stackestablishing a communication channel for communicating with the clientmachine 10 having the negotiated protocol parameters.

Still referring to FIG. 24, in some embodiments, a virtual machinecommunicates with the client machine 10 to enable negotiated protocolsas described above. As described above, a request is received from aclient machine 10 for access to a computing environment or forapplication execution, the request including an identification of a userof the client machine 10. A virtual machine in communication with ahypervisor is identified. In one embodiment, a virtual machine islaunched in communication with a hypervisor. In another embodiment, avirtual machine in communication with a hypervisor is allocated. In oneembodiment, a second virtual machine is initialized with a prescribedset of protocols and associated protocol parameters providing a commontransport mechanism. In another embodiment, the second virtual machineis initialized with a prescribed set of protocols and associatedprotocol parameters providing a common transport mechanism, wherein thecommon transport mechanism is for raw ASCII stream mode communications.

The second virtual machine creates a first portion of a protocol stack.The second virtual machine transmits a request protocol message to theclient machine 10. The second virtual machine receives from the clientmachine 10 a plurality of protocol packets specifying one or moreprotocol parameters desired by the client machine 10. The second virtualmachine transmits, in response to each received protocol packet, apacket counter-specifying one or more protocol parameters. In oneembodiment, the second virtual machine sends an acknowledgement messageto the client machine 10 indicating that at least one of the protocolsspecified by the client machine 10 has been enabled. In anotherembodiment, the second virtual machine responds to each receivedprotocol packet transmitted by the client machine 10 with a responseprotocol packet, at least one of the response protocol packets modifyingat least one of the associated protocol parameters. The first virtualmachine creates a second portion of a protocol stack, the first portionand the second portion of the protocol stack establishing acommunication channel for communicating with the client machine 10having the negotiated protocol parameters. In one embodiment, the firstvirtual machine sends an acknowledgment message to the client machine 10indicating that at least one of the protocols specified by the clientmachine 10 has been enabled. In another embodiment, the first virtualmachine responds to each received protocol packet transmitted by theclient machine 10 with a response protocol packet, at least one of theresponse protocol packets modifying at least one of the associatedprotocol parameters.

Still referring to FIG. 24, in some embodiments, a virtual machine hostserver communicates with the client machine 10 to enable negotiatedprotocols as described above. As described above, a request is receivedfrom a client machine 10 for access to a computing environment or forapplication execution, the request including an identification of a userof the client machine 10. In one embodiment, a virtual machine islaunched in communication with a hypervisor. In another embodiment, avirtual machine in communication with a hypervisor is allocated. In oneembodiment, the virtual machine host server is initialized with aprescribed set of protocols and associated protocol parameters providinga common transport mechanism. In another embodiment, the virtual machinehost server is initialized with a prescribed set of protocols andassociated protocol parameters providing a common transport mechanism,wherein the common transport mechanism is for raw ASCII stream modecommunications.

The virtual machine host server transmits a request protocol message tothe client machine 10. The virtual machine host server receives from theclient machine 10 a plurality of protocol packets specifying one or moreprotocol parameters desired by the client machine 10. The virtualmachine host server transmits, in response to each received protocolpacket, a packet counter-specifying one or more protocol parameters. Inone embodiment, the virtual machine host server sends an acknowledgementmessage to the client machine 10 indicating that at least one of theprotocols specified by the client machine 10 has been enabled. Inanother embodiment, the virtual machine host server responds to eachreceived protocol packet transmitted by the client machine 10 with avirtual machine host server protocol packet, at least one of the virtualmachine host server protocol packets modifying at least one of theassociated protocol parameters. The virtual machine host servergenerates a data structure representing the connection and associatedwith an initial protocol stack. The virtual machine host serveridentifies a virtual machine in communication with a hypervisor andgenerates a client space in the identified virtual machine. The virtualmachine host server generates a second protocol stack associated withthe generated client space and transfers the established connectionbetween the virtual machine host server and the client machine 10 fromthe initial protocol stack to the second protocol stack by associatingthe data structure with the second protocol stack.

Still referring to FIG. 24, in some embodiments, a virtual machinecommunicates with the client machine 10 to enable negotiated protocolsas described above. As described above, a request is received from aclient machine 10 for access to a computing environment or forapplication execution, the request including an identification of a userof the client machine 10. A first virtual machine in communication witha hypervisor is identified. In one embodiment, a second virtual machineis initialized with a prescribed set of protocols and associatedprotocol parameters providing a common transport mechanism. In anotherembodiment, a second virtual machine is initialized with a prescribedset of protocols and associated protocol parameters providing a commontransport mechanism, wherein the common transport mechanism is for rawASCII stream mode communications.

The second virtual machine transmits a request protocol message to theclient machine 10. The second virtual machine receives from the clientmachine 10 a plurality of protocol packets specifying one or moreprotocol parameters desired by the client machine 10. The second virtualmachine transmits, in response to each received protocol packet, apacket counter-specifying one or more protocol parameters. In oneembodiment, the second virtual machine sends an acknowledgement messageto the client machine 10 indicating that at least one of the protocolsspecified by the client machine 10 has been enabled. In anotherembodiment, the second virtual machine responds to each receivedprotocol packet transmitted by the client machine 10 with a responseprotocol packet, at least one of the response protocol packets modifyingat least one of the associated protocol parameters. The second virtualmachine generates a data structure representing the connection andassociated with an initial protocol stack. The second virtual machinegenerates a client space in the identified first virtual machine. Thesecond virtual machine generates a second protocol stack associated withthe generated client space and transfers the established connectionbetween the second virtual machine and the client machine 10 from theinitial protocol stack to the second protocol stack by associating thedata structure with the second protocol stack.

Referring now to FIG. 25, a block diagram depicts one embodiment of aclient machine 10 in communication with a remote machine 30. When aclient machine 10 wishes to access a resource provided by a remotemachine 30 , the client machine 10 may transmit a request to the generalcommunications port previously defined by the communications protocol orto the “well-known” communications port on the remote machine 30. In oneembodiment, the communication takes place by way of a datagram service.The remote machine 30 accesses the table of server addresses and returnsa message containing the address of the remote machine 30′ providingaccess to the requested resource and having the least load. In someembodiments, an address of a virtual machine executing on a remotemachine 30′ having the least load is provided. For embodiments in whichthe message identifies the execution machine having the lightest load,the operating system or hypervisor may forward the communicationrequest, and all subsequent traffic, to the appropriate virtual machine.

Subsequent communications are automatically addressed by the clientmachine 10 also to a “well-known” or predefined general communicationsport on the remote machine 30′. In one embodiment, the type of protocolwith which the initial query was made to the remote machine 30determines the protocol of the information returned by the remotemachine 30 to the client machine 10. Thus, if the request were madeusing a TCP/IP datagram, the remote machine 30 would return the TCP/IPaddress of the remote machine 30′ to the client machine 10 and theclient machine 10 would subsequently establish contact with the remotemachine 30′ using that protocol. In another embodiment, the datagramrequesting an application address by a client machine 10 includes arequest for a different type of protocol than the one used to send therequest to the remote machine 30. For example, the client machine 10 maymake a request to the remote machine 30 using the IPX protocol andrequest the address of the remote machine 30′ as a TCP/IP protocoladdress.

As described above, in connection with FIG. 8, (steps 802-804), a remotemachine 30 receives a request for access to a resource and chooses amethod for providing access to the requested resource. In someembodiments, the remote machine 30 returns the network address of aremote machine 30′ having the desired resource to the client machine 10.The client machine 10 then uses the information received from the remotemachine 30 to request connection to the specified remote machine 30′. Asis described above, such a connection is first established to a“well-known” communications port and is later transferred to a specificcommunications port under control of a connection manager. The specificcommunications port is associated with the resource executing on theremote machine 30′ which then communicates with the client machine 10through the specific communications port.

In more detail, and referring to FIG. 25, in some embodiments, a clientprocess 2502 on client machine 10 makes a request 2504 to the remotemachine 30 to obtain the address of a remote machine 30′ which includesthe desired resource 2506. The remote machine 30 returns to the clientmachine 10 a message 2508 containing the address of the remote machine30′ which includes the resource 2506. In one embodiment, the protocolused at this point of the connection is a datagram service.

The client machine 10 uses the returned address to establish acommunication channel 2510 with the remote machine 30′. The port numberused by the client machine 10 corresponds to the “well-known port” inthe remote machine 30′ which has been defined by the network protocol asthe port by which the remote machine 30′ establishes communicationconnections with client machines 10. The well-known port 2512 has arudimentary protocol stack 2514 which includes primarily an endpointdata structure 2516.

The endpoint data structure 2516 points to the communication protocolstack 76 and client connection thereby establishing a uniquerepresentation or “handle” for the client machine 10. The endpoint datastructure 2516 permits the connection between the remote machine 30′ andthe client machine 10 to be moved at will between the connection manager2518 and the various resources 2506 on the machine 30′. In someembodiments, the endpoint data structure 2516 permits the connectionbetween the remote machine 30′ and the client machine 10 to be moved atwill to or from a virtual machine providing management functionality fora virtual machine on the remote machine 30′.

The endpoint data structure 2516 , in one embodiment, not only containsthe handle to the client machine 10 but may also contain otherinformation relating to the client connection. In the embodiment shown,the machine 30′ monitors activity on a specific communications system(e.g. LAN or WAN) and has initialized this minimum protocol stack 76with only the necessary protocol modules needed to support a “TTY”communication mode. The “TTY” communication mode is a simple ASCIIstream with no protocol assumptions above the transport layer. That is,there are no protocol layers for compression, encryption, reliability,framing, or presentation of transmitted data. Thus a client machine 10seeking a resource 2506 running on the client machine 10′ establishes aconnection to the well-known communications port 2512 with the minimumprotocol set needed to support a TTY communication mode.

A connection manager 2518 executing on the machine 30′ is “listening” tothe well-known communications port 2512 for a connection request 2510.When a connection request 2510 is received from the client machine 10,the connection manager 2518 is notified 2520. The connection manager2518 knows which protocol is being used based on the notification 2520.

With this information the connection manager 2518 creates a new minimumprotocol communications stack 2522, starts a computing environment 2524(referred to throughout this discussion as an execution environment2524) and binds the new minimum protocol stack 2522 to the executionenvironment 2524. In some embodiments, the connection manager 2518creates a new minimum protocol stack 2522 in a virtual machine on theremote machine 30′. In other embodiments, the connection manager 2518creates a new minimum protocol stack 2522 in a virtual machine providingadministrative or management functionality for a virtual machineexecuting on the remote machine 30′. In still other embodiments, theconnection manager 2518 creates a plurality of minimum protocol stacks2522, each of which may be located on the remote machine 30′, in acomputing environment provided by a virtual machine executing on theremote machine 30′, or on a virtual machine providing administrative ormanagement functionality for a virtual machine executing on the remotemachine 30′.

In one embodiment, the remote machine 30′ includes a number of executionenvironments 2524 which have been previously been started, but whichhave not been associated with a communications port. In this embodiment,the pre-connection starting of the execution environments permits afaster response time than if each execution environment 2524 is startedwhen the connection request is received from the client machine 10. Whenthe execution environment 2524 is started, the resource 2506 requestedby the client machine 10 is also started. In another embodiment, if theclient machine 10 does not specify a resource, either a defaultapplication is started or the execution environment 2524 with noresource started. In some embodiments, the execution environment 2524 isthe requested resource.

The connection manager 2518 then moves the client connection, includingthe unique client identifier or handle, from the well-known port 2512 tothe new minimum protocol stack 2522. In some embodiments, the connectionmanager 2518 moves the client connection to the new minimum protocolstack 2522 in a virtual machine on the remote machine 30′. In otherembodiments, the connection manager 2518 moves the client connection tothe new minimum protocol stack 2522 in a virtual machine providingadministrative or management functionality for a virtual machineexecuting on the remote machine 30′. In still other embodiments, theconnection manager 2518 moves portions of the client connection to aplurality of minimum protocol stacks 2522, each of which may be locatedon the remote machine 30′, in a computing environment provided by avirtual machine executing on the remote machine 30′, or on a virtualmachine providing administrative or management functionality for avirtual machine executing on the remote machine 30′.

The connection manager 2518, using the minimum protocol stack 2522 sendsa TTY data stream that indicates service is available. Thus, this methodfor detecting a client connection is independent of the port to whichthe connection is first established. If the client machine 10 does notrespond within a prescribed time period (e.g. 5 seconds) to the serviceavailable message, a resend of the “service available” message isperformed by the machine 30′.

If the client machine 10 receives the message, the client machine 10sends a TTY string indicating that the “service available” message wasdetected. The client machine 10 waits for the machine 30′ to respond andif the response is not within a prescribed time interval (e.g. 5seconds) the client machine 10 resends the message. The connectionmanager 2518 then queries 90 the client machine 10 asking for theclient's default communication parameters. This query 90 takes the formof a message which is passed back to the client machine 10 and whichindicates that the client machine 10 should respond with detailsregarding what protocols the client machine 10 would like to use in theconnection.

In response, the client machine 10 sends a set of protocol packets 2526;each packet of which is used to specify a required or optional protocolmodule that is being requested from the remote machine 30′. In oneembodiment, the number of packets in the set is variable with one packetbeing sent for each protocol requested. In another embodiment, thenumber of packets that is being sent is included in the header of thefirst packet. In a third embodiment, the remaining number of packetsbeing sent is included in the header of each packet and is decrementedwith each succeeding packet sent. Thus, the client machine 10 mayrespond to the query 2528 by indicating that, for example, encryptionand data compression will be used. In such a case, two protocol packetswill be sent from the machine client 10 to the remote machine 30′ and,in one embodiment, the header of the first packet will indicate thenumber of packets as two.

Once the responses to the query 90 have been received, the connectionmanager 2518 builds a protocol stack using protocol drivers 2530, 2530′,2530″ which correspond to the protocols requested by the client machine10. In one embodiment, the connections manager 2518 places each of therequired protocol drivers 2530, 2530′, 2530″, corresponding to therequested client protocols (e.g. an encryption driver if encryption isdesired by the client) into the protocol stack “container” 2532 andlinks them together. In some embodiments the connections manager 80places protocol drivers 2530, 2530′, 2530″ into a plurality of protocolstack “containers” 2532 residing in different locations and links theplurality of protocol stack “containers” 2532. This dynamic processallows a client machine 10 to specify the contents of a protocol stackdynamically without requiring that the machine 30′ have a prior protocolstack description for a particular client machine 10. Using this method,multiple client machines 10 may be served by a single machine 30, evenif the separate client machines 10 have vastly differing requirementsfor the associated communications channel. In the embodiment shown, eachclient machine 10, 10′, 10″ is associated with a respectivecommunications protocol stack 2522, 2522′ and 2522″. Such dynamicallyextensible protocol stacks are described in more detail below.

In the embodiment just discussed, the “container” 2532 is a user levelor kernel level device driver, such as an NT device driver. Thiscontainer driver provides ancillary support for the inner protocolmodules or “drivers” (generally 2530) which correspond to the protocolrequirements of the client machine 10. This ancillary support is in theform of helper routines that, for example, aid one protocol driver totransfer data to the next driver. Alternatively, in another embodimenteach protocol driver is a complete user-level or kernel-level driver initself.

Referring now to FIG. 26, the viewing user uses a so-called “browser”program to display an HTML page 2602 having a resource window 2604 onthe screen 2606 of the user's client machine 10. Once the viewing userhas indicated that execution of the resource 2506 should commence, thebrowser application 2706 instantiates a parameter handler 2708 andpasses the instantiation parameters associated with the resource window2604 by the generic embedded window tag 2704. The parameter handler 2708instance spawns a network executive 2710 and passes to it the parametersof the resource window 2604. The network executive 2710 determines whichresource 2506 is to be invoked, and on what machine 30′ that resource2506 resides. Generally this information is passed to it by theparameter handler 2708 instance which gets it from the browserapplication 2706 in the form of the generic embedded window tag 2704,but the network executive 2710 may need to query another remote machine30, in order to determine which servers, if any, host the desiredresource 2506. The network executive 2710 then begins execution of theresource and displays the output of the resource 2506 in the resourcewindow 2604 as described in detail above.

The network executive 2710 continues to directly display resource outputin the resource output window 2604′ until the viewing user indicatesthat execution of the resource 2506 should stop, e.g. by closing theresource window 2604, or until the viewing user clicks on a tagindicating that a different HTML page should be displayed. When thisoccurs, execution of the resource 2506 can be terminated. It ispreferred, however, is to “cache” the connection. In effect, the firstparameter handler 2708 instance is not immediately terminated. However,the resource 2506 continues executing with a reduced priority level,i.e. in “background” mode, because the first parameter handler 2708 nolonger has “focus”.

In general, it is desirable to accomplish connection caching byproviding the parameter handler 2708 source code with a globallyaccessible data structure for registering instances. For example, theparameter handler 2708 may be provided with a globally accessible linkedlist data structure, data array, data table, or other data structure.Because the data structure is globally available, each instance of theparameter handler 2708 is able to read and write the data structure.This allows each instance of the parameter handler 2708 to “register”with every other instance by writing to the data structure to signal itsexistence.

For embodiments in which no other connection information is stored, apredetermined limit on the number of connections that may be cached atany one time can be set. In these embodiments if registration of aninstance would result in an excess number of cached connections, one ofthe “cached” connections is removed, i.e. the parameter handler 2708instantiation associated with that connection is notified that it shouldterminate. Before termination, the parameter handler 2708 notifies itsassociated network executive 2710 that it should terminate. In turn, thenetwork executive 2710 closes its session with the server hosting theresource 2506 and then terminates.

In embodiments in which other information is stored, the additionalinformation may be used to more effectively manage the cachedconnections. For example, if a user has not actively viewed an HTML page2602 in a predetermined number of minutes, e.g. ten minutes, theparameter handler 2708 instantiation is instructed to terminate, thesession with the hosting server is terminated, and the parameter handler2708 instance removes its entry in the registry.

Cached connection information may be managed using any known cachemanagement scheme. Connection entries may be discarded on a “first in,first out” basis, i.e. the oldest entry is discarded each time a newentry must be added. Alternatively, cached connection informationentries may be discarded on a “least recently used” basis, whichdiscards information relating to connections which have been used theleast amount by the user. Other cache management techniques, such asrandom replacement, may also be used.

If the viewing user returns to a previous HTML page 2602 having a cachedconnection, the network executive 2710 associated with the HTML page2602 is returned to the foreground, i.e., it regains “focus”, andprocessing of the associated resource resumes at a normal prioritylevel. If necessary, the network executive 2710 re-establishes theconnection with the resource 2506. Although no output data is stored bythe network executive 2710 for cached connections, as soon as aconnection is re-established for a resource window 2604 the connectionto the resource 2506 is re-established and the resource 2506 againwrites directly to the resource window 2604.

Referring to FIG. 27, an HTML file 2602 located on a machine 30′ andconstructed in accordance with an embodiment of the invention includes ageneric embedded window tag 2704. The generic embedded window tag 2704is any data construct which indicates to a browser 60 displaying theHTML file 2602 that a generic embedded window 2604 should be displayedat a particular location in the HTML page 2602 described by the HTMLfile 2602. The generic embedded window tag 2704 may include additionalinformation, such as height of the window, width of the window, borderstyle of the window, background color or pattern in the window, whichresources may be displayed in the window, how often the output displayshould be updated, or any other additional information that is useful toenhance display of the resource output.

Some examples of generic embedded window tags that can be embedded in anHTML file follow. ActiveX tag  <objectclassid=“clsid:238f6f83-b8b4-11cf-8771-00a024541ee3”  data=“/ica/direct.ica” CODEBASE=“/cab/wfica.cab”   width=436height=295>   <param name=“Start” value=“Auto”>   <param name=“Border”value=“On”>  </object> Netscape Plugin tag  <embedsrc=“http://www.citrix.com/ica/direct.ica”  pluginspage=“http://www.citrix.com/plugin.html”   height=295 width=436Start=Auto Border=On>  <embed> JAVA tag  <applet code=JICA.classwidth=436 height=295>   <param name=Address  value=“128.4.1.2602”>  <param name=InitialProgram value=Microsoft Word 7.0>   <paramname=Start  value=Auto>   <param name=Border  value=On>  </applet>

In each case above, the tag indicates that a window having a height of295 pixels and a width of 436 pixels should be drawn to receive resourceoutput. Each tag also specifies that the resource should automaticallystart execution and that the window in which the resource output isdisplayed should be drawn with a border. The ActiveX and Netscape Plugintags have the remote resource parameters specified in the file“direct.ica” located in the directory “/ica.” The JAVA tag specifies theremote resource parameters directly. In the example above, the addressof the machine 30 hosting the resource is specified as well as the nameof the resource to be executed.

The browser application 2706 accesses the HTML file 2602 by issuing arequest to a specific Uniform Resource Locator (URL) address. Themachine 30′ hosting the HTML file 2602 transmits the HTML file 2602 datato the browser application 2706, which displays text and translates anytags that are included in the HTML file 2602. The browser application2706 displays the HTML file 2602 data as an HTML page 2602. If a genericembedded window tag 2704 is present in the HTML file 2602, such as oneof the tags described above, the browser 60 draws a blank window 2604 inthe displayed HTML page 2602.

Execution of the desired resource 2506 may commence immediately upondisplay of the HTML page 2602 or execution may await some signal, e.g. aspecified user input which indicates execution of the resource 2506should begin. Once execution of the resource 2506 is commenced, thebrowser application 2706 instantiates a parameter handler 2708associated with the resource window 2604. The parameter handler 2708instance may be spawned as a child process of the browser application2706, as a peer process of the browser application 2706, astatically-linked thread of execution, a dynamically-link thread ofexecution, or as a Dynamically Linked Library (“DLL”) associated withthe browser application 2706.

The browser application 2706 passes any specific parameters associatedwith the resource window 2604 that were provided by the generic embeddedwindow 66 tag to the parameter handler 2708 instance. Additionally, thebrowser application 2706 may pass the handle for the resource window2604 to the parameter handler 2708 instance or the parameter handler2708 instance may query the browser application 2706 to retrieve thehandle for the resource window 2604. The parameter handler 2708 instancealso spawns a network executive 2710. The network executive 2710 may bespawned as a child process of the parameter handler 2708 instance, astatically-linked thread of execution, a dynamically-link thread ofexecution, or as a peer process of the parameter handler 2708 instance.

The parameter handler 2708 instance forwards any specified resourcewindow 2604 parameters to the network executive 2710. Parameters whichare not specified by the parameter handler 2708 instance or the embeddedgeneric window tag 2704 may be set to default values. The networkexecutive 2710 may have certain parameter defaults hard-coded, or thenetwork executive 2710 may access a file which contains parameterdefaults.

The network executive 2710 creates its own resource output window 2604′.The network executive 2710 creates its resource output window 2604′ as achild of the displayed resource window 2604 and displays its resourceoutput window 2604′ directly over the parent window 2604 drawn by thebrowser application 2706. Since the resource output window 2604′ drawnby the network executive 2710 is a child of the resource window 2604drawn by the browser application 2706, the resource output window 2604′inherits various properties of its parent including positioninformation. Accordingly, the resource output window 2604′ will followthe resource window 2604 as the viewing user scrolls the screen of thebrowser application 2706 or performs other actions which vary theposition of the resource window 2604.

The network executive 2710 also establishes a communications channelwith the machine 30′ and invokes execution of the desired resource 2506by the machine 30′ using the connection methodology described above. Thenetwork executive 2710, which acts as the client machine 10 in the abovedescription, passes any parameters it received from the parameterhandler 2708 instantiation to the machine 30′, along with any necessarydefault values. If a parameter is not passed to the machine 30′, themachine 30′ may request the parameter if it is a necessary parameterwhich has no default value, e.g. “user id,” or it may provide a defaultvalue for the parameter, e.g. execution priority. The machine 30′ beginsexecution of the desired resource 2506 and directs the output to thenetwork executive 2710. The network executive 2710 receives data fromthe resource 2506 and displays the output data in its resource outputwindow 2604′. Since the resource output window 2604′ is drawn on top ofthe resource window 2604 drawn by the browser application 2706, theresource output data is displayed in the HTML page 2602. As noted above,the resource output window 2604′ drawn by the network executive 2710 isa child of the resource window 2604 drawn by the browser application2706. This allows the resource output window 2604′ to scroll as the HTMLpage 2602 is scrolled

The resource output window 2604′ also receives input from the viewinguser. Raw input data, e.g. a mouse click, is received into the resourceoutput window 2604′ by the network executive 2710. The network executive2710 forwards the raw input data to the resource 2506 executing on themachine 30″ In this manner, the viewing user is able to interact withthe resource 2506 via the HTML page 2602.

Referring now to FIG. 28, and in brief overview, an embodiment of aninteractive hypermedium system of the invention includes a clientmachine 10, a network remote machine 30 and an execution remote machine30′ interconnected by a communications link 150, herein referred towithout any loss of generality as a network or web. The network remotemachine 30 may be provided by a remote machine 30. The execution machine30′ may be provided by a physical machine or a virtual machine.

A user on a client machine 10 wishing to access the resource 2802 whichis located on the execution machine 30′ on the web 150 does so through agraphical user interface 2804, which is herein referred to without anyloss of generality as a hypermedium, located on the client machine 10.The graphical interface is displayed on a graphical display device 124.Data is entered by a mouse 16 and a keyboard 17 located on the clientmachine 10. The graphical display or page 2806 which the user firstviews on the hypermedium 2804 is referred to herein without any loss ofgenerality as the home page or web page of the resource 2802. A page2806 or home page of the hypermedium 2804 includes a graphic link 2808or textual link 2810 herein referred to without any loss of generalityas a hyperlink. The web page is displayed by a process 2602 referred toherein without any loss of generality as a network browser 2602executing on the client machine 10.

The network browser 2602 obtains the first page or web page 2806 from anetwork remote machine 30 and displays the web page 2806 on thehypermedium 2804 for the user to view on the graphical display device124. When the user selects a resource 2802 to access (by selecting agraphical 2808 or textual 2810 hyperlink using the mouse 16 or keyboard17) the network browser 2602 obtains a network configuration file 2812corresponding to the selected resource 2802 from a predetermined networkserver 2606 and starts a client agent 2814 which will communicate withthe selected resource 2802. This will be discussed in more detail below.

The client agent 2814 reads the configuration file 2812 and establishesa communications link to a server agent 2816 on the execution server 24specified by the configuration file 2812. In one embodiment, theconfiguration file 2812 includes the name of the resource and the nodelocation of the resource 2802 corresponding to the hyperlink 2808, 2810.The configuration file may also contain optional information such asauthentication or authorized user information. Server agent 2816performs the operations necessary (such as authentication) to permit theclient agent 2814 access to the resource 2802, and once access ispermitted, allows access to the resource 2802 requested by the user. Theserver agent 2816 may execute in a hypervisor, a virtual machine, or onan operating system. In some embodiments, the functionality provided bythe server agent 2816 is split between a hypervisor and a virtualmachine or between two virtual machines. In still other embodiments, thefunctionality provided by the server agent is split between a hypervisorand a guest operating system executing in a virtual machine. In someembodiments, a connection to a computing environment including theresource 2802 is established, as described in further detail below.

Once the resource 2802 is available on the execution server 30′, theclient machine 10 may access the resource 2802 through the server agent2816 directly with the client agent 2814 without intervention by thenetwork browser 2602. The client agent 2814 is then responsible forreceiving data from the user through the mouse 16 and keyboard 17 andtransmitting it to the resource 2802 on the execution machine 30′.Similarly, the client agent 2814 is responsible for receiving data fromthe resource 2802 on the execution machine 30′ and displaying the datain a display window 2818 on the graphical display device 124 on theclient machine 10. It should be noted that the display window 2818 maybe located within the boundaries or outside the boundaries of thehypermedium 2804. When the resource 2802 is completed the server agent2816 instructs the client agent 2814 to disconnect the communicationlink 150 between the client agent 2814 and the server agent 2816. Insome embodiments, the server agent 2816 may reside outside of theexecution machine 30′. In other embodiments, the client agent 2814 mayreside outside of the client machine 10.

FIG. 29 depicts the operation of the system in more detail. Initially,the client agent 2814 is registered (step 2901) with the network browser2602 of the client machine 10 and an entry is made in the networkbrowser's registration file 2820 (FIG. 28). This entry permits thenetwork browser 2602 to start the client agent 2814 whenever a givenfile type (including types such as a MIME type) is requested by thehyperlink 2808,2810 of the hypermedium 2804. In this case the clientagent 2814 is designed to permit a user on the client machine 10 toexecute and interact with a remote resource 2802 on an execution machine30′. The client agent 2814 would be registered with the network browser2602 such that whenever a hyperlink 2808, 2810 requested the given filetype (for example .RMT for remote execution) from the network browser2602, the network browser 2602 would start the client agent 2814 whichwould permit remote execution and interaction with a resource 2802resident on an execution machine 30′. The invoking of the client agent2814 is discussed in more detail below.

When a user wishes to access a resource from a hypermedium environment,for example a database program, the hypermedium 2804 is displayed in amanner that is well known to those skilled in the art. When the userselects a hyperlink 2808, 2810 on the page 2806 of the hypermedium (step2902) by using the mouse 16 or keyboard 17 on the client machine 10, arequest is made to the network browser 2602 for the corresponding datafile (step 2903). In this example, the file type (.RMT) is requested.

The network browser 2602 obtains the corresponding configuration file2812 from the network server 2606 which is specified in the file requestmade by the hyperlink 2808, 2810 to the network browser 2602 (step2904). The network browser 2602 then compares the obtained configurationfile 2812 with the registration file 2820 of client agent names which itmaintains (step 2905). In one embodiment, the network browser 2602compares a file type of the obtained configuration file 2812 with theregistration file 2820. In another embodiment, the network browser 2602compares an entry in the obtained configuration file 2802 with theregistration file 2820. If the client agent 2814 specified by theconfiguration file 2812 is found in the registration file 2820, theclient agent 2814 is started (step 2906).

The invoked client agent 2814 reads the configuration file 2812 (step2907), and based upon the information in the configuration file 2812,begins to establish a communication link with the server agent 2816 onthe execution server 24 (step 2908), in this case the sales databaseapplication execution server (generally 30′).

Considering the process of beginning the communications link of step2908 (FIG. 29) in more detail, communication begins with the serveragent 2816 monitoring communication activity on the network 150. At thispoint, no protocol assumptions are made by the server agent 2816 beyondthose necessary for the transport layer. Similarly, the client agent2814 also makes no assumption of the communications protocol beyond thatrequired by the transport layer. Once the server agent 2816 determinesthat a client agent 2814 is attempting to communicate with it, theserver agent 2816 transmits a message to the client agent 2814indicating that service is available.

Once the client agent 2814 determines that service is available on theexecution remote machine 30′, the client agent 2814 transmits a messageto the server agent 2816 indicating that it is ready to proceed with thecommunication protocol. Once the server agent 2816 has responded that itis ready to continue the communication protocol, the client agent 2814enables the protocol necessary for it to run the application 36. Inresponse to the message from the client agent 2814, the server agent2816 also enables the required protocol. The server agent 2816 thentransmits a message using the required protocol indicating that theclient agent's request has been received and accepted.

In response the client agent 2814 and the server agent 2816 exchange aset of messages which negotiate the parameters under whichcommunications will occur. Once negotiations are complete, the clientagent 2814 and the server agent 2816 are able to communicate asnecessary for the resource 2802 to be run by the user.

Once the communications protocol has been established and the serveragent 2816 has authenticated the client agent 2814 (step 2909) (forexample determining that the user has permission to read and write tothe database) access to the resource 2802 (step 2910) is provided by theapplication execution server 24. At this point resource 2802 on theexecution server 30′ is communicating via the server agent 2816 with theclient agent 2814 on the client machine 10. The client agent 2814 is nowresponsible for transmitting data input by the user using the mouse 16and keyboard 17 to the resource 2802 on the execution machine 30′.Further, the client agent 2814 is responsible for receiving data fordisplay from the resource 2802 and displaying that data in theapplication window 2818 on the graphical display device 124 of theclient machine 10.

It should be noted that the underlying presentation protocol whichpasses data to a transport layer such as TCP/IP must be capable oftransferring graphical information. Examples of such protocols which maybe used for interactive hypermedia communication include public domainX11 protocol, the proprietary Independent Computing Architecture (ICA)protocol of Citrix Systems Inc., or the proprietary Remote DesktopProtocol (RDP) of Microsoft Corporation.

Thus the above described system permits a user on a client machine 10,which may have very limited resources, to start and interact with aresource 2802 located on an execution machine 30′. The resource 2802then runs on the execution machine 30′ and the data is input and theresults displayed on the client machine 10. In some embodiments, theaccessed resource 2802 executes in a virtual machine provided by theremote machine 30′.

Referring now to FIG. 30, a flow diagram depicts an embodiment of methodof making a hypermedium page interactive, the hypermedium page displayedby a network browser. As described above, a hyperlink on a hypermediumpage displayed on a client machine 10 is selected, the hyperlinkidentifying a desired computing resource (step 3002). A hyperlinkconfiguration file is retrieved, the hyperlink configuration filecorresponding to the hyperlink and identifying a remote machine 30′(step 3004). A client agent is started on a client machine 10 (step3006). The client agent creates a communication link to a virtualmachine executing on the remote machine 30′ identified by the hyperlinkconfiguration file (step 3008). The client agent receives data from thevirtual machine and displays on the client machine 10 the received datawithout intervention by the network browser (step 3010).

A hyperlink on a hypermedium page displayed on a client machine 10 isselected, the hyperlink identifying a desired computing resource (step3002). In one embodiment, the hypermedium page is obtained from a remotemachine 30 prior to selection of the hyperlink on the hypermedium page.In another embodiment, the hypermedium page is received responsive to arequest for an enumeration of available resources.

A hyperlink configuration file is retrieved, the hyperlink configurationfile corresponding to the hyperlink and identifying a remote machine 30′(step 3004). In one embodiment, a remote machine 30, functioning as abrokering machine, identifies the remote machine 30′. In anotherembodiment, the remote machine 30′ functions as an execution machine. Instill another embodiment, a hypervisor executes on the remote machine30′. In yet another embodiment, a virtual machine is launched into ahypervisor executing on the remote machine 30. In some embodiments, aserver agent starts on a virtual machine in the remote machine 30′.

A client agent is started on the client machine 10 (step 3006). In oneembodiment, the client agent is started by the network browser upon asuccessful match of an entry in the hyperlink configuration file with anidentifier associated with the client agent in a registration fileaccessible by the network browser. In another embodiment, the clientagent is registered with the network browser.

The client agent creates a communication link to a virtual machineexecuting on the remote machine 30′ identified by the hyperlinkconfiguration file (step 3008). In one embodiment, execution of anidentified application program begins on the virtual machine in responseto the created communication link. In another embodiment, the clientagent creates the communication link without intervention by the networkbrowser.

The client agent receives data from the virtual machine and displays onthe client machine 10 the received data without intervention by thenetwork browser (step 3010). In one embodiment, the data received fromthe virtual machine is displayed in a display window on the clientmachine 10. In some embodiments, a presentation layer protocol isemployed for communication over the communication link.

Referring back to FIG. 28, in some embodiments of a system for making ahypermedium page interactive, access to a requested computingenvironment is provided through the interactive hypermedium page. Theclient machine 10 executes a browser application 2602. A remote machine30 functions as a network server 2606 and transmits a networkconfiguration file to the client machine 10. A client agent 2814executing on the client machine 10 establishes a communications linkwith a remote machine 30′, functioning as an execution machine 30′.

As described above, the client machine 10 executes a browser application2602, which displays a hypermedium page including a hyperlinkidentifying a resource 2802. A remote machine 30 functions as a networkserver 30 and transmits, in response to selection of said hyperlink, anetwork configuration file to the client machine 10, the networkconfiguration file corresponding to said identified computing resource2802. In some embodiments, a process obtains the hypermedium page fromthe network server 30 and provides the hypermedium page to the clientmachine 10.

In one embodiment, the network configuration file comprises a resourceidentifier corresponding to said hyperlink and a virtual machine addresscorresponding to said hyperlink. In some embodiments, the virtualmachine address is a virtual IP address provided by a hyperlink in whichthe virtual machine executes. In other embodiments, the virtual machineaddress is an IP address associated with an execution machine 30′ onwhich the virtual machine executes.

A client agent 2814 executing on the client machine 10 establishes acommunications link with a remote machine 30′, functioning as anexecution machine 30′. The client agent 2814 establishes the linkresponsive to data in the network configuration file. In one embodiment,a hypervisor executes on the execution machine 30′ and a virtual machineproviding the resource 2802 executes in the hypervisor. In someembodiments, the virtual machine transmits data to the client agent 2814for display without intervention by the browser application 2602. In oneof these embodiments, the virtual machine provides access to therequested resource 2802 and the data is output from an execution of therequested resource 2802.

In some embodiments, the client agent establishes, responsive to data inthe configuration file, a communications link with a management programexecuting on a remote machine. In one of these embodiments, themanagement program executes on the network server 2606. In another ofthese embodiments, the management program executes on the executionmachine 30′. In still another of these embodiments, the managementprogram executes on a virtual machine in the execution machine 30′. Inyet another of these embodiments, the management program executes on avirtual machine having management privileges on the execution machine30′ or on a remote machine 30″. In other embodiments, the managementprogram launches the virtual machine providing the desired computingresource into a hyperlink on the execution machine 30′.

In some embodiments, the client agent 2814 displays data received fromsaid virtual machine in a display window located at the client machine10. In one of these embodiments, the display window is located withinthe boundaries of the hypermedium page. In another of these embodiments,the display window is located outside the boundaries of the hypermediumpage.

Referring to FIG. 31, in some embodiments of the methods describedabove, data transmitted by the resource 2506 is sent to other remotemachines 30 prior to being sent to client machines 10. In this manner,data transmitted by the resource 2506 is transmitted to an increasingnumber of client machines 10 as the network fans out.

When each client machine 10 terminates its connection with the machine30′, each client protocol stack (generally 2522) and its associatedminimal stack (generally 3102) is destroyed. Similarly, the minimalprotocol stack (generally 3104) associated with the first clientprotocol stack 2522 is also destroyed. When the last of the minimal 3102and second (and subsequent) client protocol stacks 2522 has terminated,the configuration is as it was initially with only a first clientcommunications protocol stack 2522 associated with the executionenvironment 2524. Note that until all the second and subsequent clientprotocol stacks 2522 are terminated, the first client protocol stack2522 may not be destroyed, even if the client machine 10 is no longerpresent.

As shown in FIG. 25 above, each execution environment 2524 communicateswith each protocol stack 2522 through a multiplexer 2534, 2534′, 2534″.Now referring also to FIG. 31, it is possible for more than one machine10 to receive data being transmitted to the client machine 10, forexample, in order to shadow or monitor the transmission of data from amachine 30′ or to broadcast data from a specialized broadcastapplication, such as a stock quotation application, from which the samedata is broadcast or transmitted substantially simultaneously to anumber of clients (generally 10).

In such a case, the client machine 10 causes the specialized resource2506 to execute and transmit its data to the client machine 10 asdiscussed previously. When a client machine 10′ requests access to thebroadcast resource 2506, the connection manager 2518 begins to constructthe protocol stack 2522′ for the second client machine 10′ as previouslydiscussed with regard to the first client machine 10. However, becausethe resource 2506 is a broadcast application, the connection manager2518 recognizes that it need not start an additional executionenvironment 2524 and instead takes the steps necessary to send the datafrom the broadcast resource 2506 to the client machine 10 and anyadditional machine 10″.

First, the connection manager 2518 creates a first minimalcommunications protocol stack 3104 which it associates with acommunications protocol stack 2522 of the first client machine 10. Theconnection manager 2518 next creates a second minimal protocol stack3102 and associates it with the communications protocol stack 2522′ ofthe second client machine 10′. As each additional client machine 10″requests access to the broadcast resource 2506, another minimal protocolstack 3104′ is created and associated with the first client protocolstack 2522 and another minimal protocol stack 3102′ and client protocolstack 2522″ is created for each new client machine 10″. The first clientprotocol stack 2522 and all the minimal protocol stacks 3104, 3104′associated with the first client protocol stack 2522, and each pair ofclient protocol stacks 2522′, 2522″ and minimal protocol stacks 3102,3102′ associated with each additional machine 10′, 10″ are incommunication by way of a multiplexer 2534.

In some embodiments, the connection manager 2518 resides outside of avirtual machine executing on a remote machine 30′ and creates minimalprotocol stacks 3102 within the virtual machine executing on the remotemachine 30′. In other embodiments, the connection manager 2518 residesoutside of a virtual machine executing on a remote machine 30′ andcreates minimal protocol stacks 3102 within a second virtual machineproviding management and administrative functionality for the virtualmachine executing on the remote machine 30′. In still other embodiments,the connection manager 2518 resides outside of a virtual machineexecuting on a remote machine 30′ and creates minimal protocol stacks3102 within a hypervisor providing management and administrativefunctionality for the virtual machine executing on the remote machine30′. In yet other embodiments, the connection manager 2518 residesoutside of a virtual machine executing on a remote machine 30′ andcreates minimal protocol stacks 3102 within a host operating system onthe remote machine 30′ providing management and administrativefunctionality for the virtual machine executing on the remote machine30′. In some embodiments, the connection manager 2518 resides inside avirtual machine executing on a remote machine 30′ and creates minimalprotocol stacks 3102 within the virtual machine executing on the remotemachine 30′.

When a multiplexer 2534 is directing data to or receiving data from onlyone machine 10, the multiplexer 2534 is acting as a simple pass-throughdevice. However, when there is more than one client machine 10, 10′, 10″receiving data from or transmitting data to a single resource 2506, eachmultiplexer (generally 2534) takes on two additional configurations. Inone configuration, the multiplexer 2534 is configured to send resourcedata to or receive data from both the first client protocol stack 2522and each of the minimal communications protocol stacks 3104, 3104′associated with it. In the second configuration the multiplexer 2534 isconfigured to send data received by the minimal protocol stack 3102,3102′ to the client protocol stack 2522′, 2522″, respectively,associated with it. In this embodiment, the multiplexer 2534 may receiveinput data directly from each client protocol stack 2522, 2522′, 2522″.

The connection manager 2518 connects the minimal protocol stacks 3104,3104′ associated with the client machine 10 with the minimal protocolstacks 3102, 3102′ respectively, of the second client machine 10′ andsubsequent client machines 10″ and instructs the multiplexer 2534 todirect output from the resource 2506 to the communications protocolstack 2522 of the client machine 10 and its associated minimal protocolstacks 3104, 3104′. The multiplexer 2534 is also instructed by theconnection manager 2518 to connect each second and subsequent clientminimal protocol stack 3102, 3102′ to its associated client protocolstack 2522, 2522′, respectively. Data transmitted to the client machine10 by way of the first client protocol stack 2522 is therefore alsotransmitted to the minimal protocol stacks 3104, 3104′ associated withthe client machine 10 and hence to the client machine 10′ and subsequentclient machines 10″ by way of their associated protocol stacks 2522′,2522″, respectively, and associated minimal protocol stacks 3102, 3102′,respectively. In one embodiment, the protocol stack container includes adata structure to keep track of the number and type of protocolsassociated with a given resource 2506.

Referring to FIG. 32, as discussed above, it is possible that the“clients” of one machine 30′ be other remote machines 30′ and 30″ (onlytwo being shown for simplicity). The remote machines 30′ and 30″ thentransmit the data to client machines 10 or to additional remote machines30′. In this embodiment the output of the server protocol stack(generally 2522) is connected to the protocol stacks 107′ of thesecondary remote machines 30′ and 30″. Then as described previously, thedata is transmitted between the protocol stacks and out to the clientmachines 10. In this manner the data may fan out and be distributed tomany more clients than may reasonably be supported by one server. Insome embodiments, the output of the server protocol stack may beconnected to protocol stacks 3102′ created in virtual machines executingon remote machines 30.

In brief overview, in one embodiment of the methods described above, auser of a client machine 10 requests access to one or more resourcesfrom a remote machine 30, which may provide web server functionality.After authenticating the user's credentials, the web server accessesuser-specific and resource-specific parameters from a memory coupled tothe web server. The web server subsequently communicates theseparameters to one or more remote machines 30 hosting the requestedresources, and software processes operating on the resource serversexecute and initialize the requested resources using the communicatedparameters. In this manner, each instance of the resources ispersonalized for a particular requesting user. The particular networkaddresses of the resource servers hosting these personalized applicationprograms are then forwarded to the user's client machine 10, whichestablishes a communications link and client-server session therewith.

Commands, events, graphical data, and window attribute informationassociated with the executing resources are communicated between theuser device and the resource servers during the client-server session toensure that the resource-output data is displayed seamlessly on thedesktop of the user device. Seamless display of the resource-output datarefers to the presentation of the data on the user desktop in a mannerthat is consistent with how locally-executing resources are presentedand manipulated in the local desktop of the user device. A user maytherefore view and interact with the resource-output data generated bythe remote resources as if the resources were being executed locally.

In one embodiment, the output of the resources is displayed in one ormore resource-output windows positioned within a web page displayed by aweb browser of the user's device. The resource may be executing on aremote machine 30 or on a virtual machine executing on the remotemachine 30. In a further embodiment, the attributes of theresource-output windows can be modified so that the resource-outputwindows are moveable and resizeable within the boundaries of the webpage. In another embodiment, the resource-output windows initiallyappear within the boundaries of the web page and are subsequentlymoveable so that they are positioned outside the boundaries of the webpage and thus give the appearance that the application-output windowscorrespond to locally-executing applications rather than toremotely-executing applications. In yet another embodiment, theapplication-output windows initially appear outside the boundaries ofthe web page and thus also appear to correspond to locally-executingapplications. In one embodiment, the application output displayed in theapplication-output windows and the attributes of the application-outputwindows themselves are communicated and manipulated by softwareprocesses on the user's device and on the resource servers, withoutinvolvement of the web server or web browser that initially providedaccess to the resources.

In more detail and with reference to FIG. 33, a server-based computingarchitecture 3300, capable of providing remote users with web-access tothe full functionality of web and legacy applications (e.g., unmodifiedapplication programs that are not designed for web-based delivery),includes a client machine 10 (e.g., any digital data processing device),a web server 3304, one or more remote machines 30 that are eitherstandalone or clustered within a machine farm 38 and which arepreferably protected by a firewall 3302, and a data communicationsnetwork 150 (e.g., Internet, Intranet, etc.) that provides the necessaryconnectivity to enable each of these elements to communicate with eachother.

In other embodiments, the web server 3304 is a remote machine 30. Insome of these embodiments, virtual machines may be executing on one ormore of the remote machines 30, the virtual machines providing computingenvironments in which a requested resource resides and generatesresource-output data.

In operation and also with reference to FIG. 28, a user of the clientmachine 10 directs a browser 2822 executing on the client machine 10 tosubmit a request for access to particular web page content 3306accessible via the web server 3304. In one embodiment, the user enters auniversal resource locator (“URL”) address into the browser 2822. TheURL is associated with the web page content 3306 hosted by the webserver 3304 and the browser 2822 responds by transmitting the requestfor access to the appropriate URL address.

The web server 3304 receives the request for access, which typicallyincludes user credential information (e.g., user ID, password,group/project membership identifier, etc.), and authenticates the userto the machine farm 38 or to the individual servers 114 that provide atleast some of the web page content 3306.

The web server 3304 authenticates the user by accessing anauthentication process that compares the credentials entered by the userwith previously-assigned credentials. In one embodiment, theauthentication process and database of previously-assigned credentialsare stored and maintained on the web server 3304. In other embodiments,the previously-assigned credentials can be stored in the machine farm38, on individual application remote machines 30, and/or on anadministrative server (not shown) that is coupled to the web server 3304via the Internet or other data communication network.

In the scenario where the web page content 3306 corresponds to anenterprise portal, which provides access to a resource set 3308 (e.g.,the set of resources that have been personalized for the user by aportal administrator), the web server 3304 accesses one or more resourceobjects 3310 (e.g., COM-compliant Java objects, ActiveX objects, HTMLtags, etc.) that call web server-side scripts to authenticate the userand/or to obtain the resource set 3308 information associated with theportal and user from the machine farm 38. The resource objects 3310 alsoinclude properties that are associated with the user and/or theparticular resources 3312 in the resource set 3308 that are provided viathe portal. The user properties include, for example, group/projectinformation that identifies the particular resources 3312 and data thatthe user needs to access in order to allow the user to collaborate withother members of the group/project. The resource properties include, forexample, the user's preferences for each of the resources 3312 in theresource set 3308.

The scripts called by the resource objects 3310 establish a networksession between the web server 3304 and the machine farm 38 via, forexample, a central administrative process (not shown), which monitorsand controls each resource machine 30 in the machine farm 38. Theadministrative process selects one or more resource servers, which hostthe resources 3312 in the resource set 3308 specified by the resourceobjects 3310, based, for example, on a server and/or network performancebasis. The desired resource set 3308 can be provided entirely by asingle server 30 by selecting/allocating each resource 3312 in theresource set 3308 from a plurality of resources 3312, 3314 hosted on theserver 30. Alternatively, the resource set 3308′ can be provided by aplurality of remote machines 30 with each machine 30 hosting at leastone of the resources in the resource set 3308′.

The administrative process launches one or more server agents 3316 onthe selected/allocated remote machines 30 in response to the scriptscalled by the resource objects 3310. Server agents 3316 are softwareprocesses that execute, initialize, and interact with each of theresources 3312 in the resource set 3308 in accordance with theproperties specified by the resource objects 3310. In one embodiment,there is a server agent 3316 for each resource 3312 in the resource set3308. In other embodiments, there is a single server agent 3316 for theresource set 3308, to the extent that all of the resources 3312 arehosted on the same server 30. In yet another embodiment, there is asingle server agent 3316 for each server 30. The server agents 3316 thenprovide the output of the resources 3312 in the resource set 3308 aswell as any other information relating to the resource set 3308 to theweb server 3304, which subsequently formats the resource set informationinto the web page content 3306. The web page content 3306 can includeapplication icons corresponding to one or more of the resources 3312 inthe resource set 3308 as well as resource-output data from one or moreof the resources 3312. In one embodiment, the resource-output dataprovided by the resources 3312 corresponds to graphical data that isformatted to fit into a window, which exhibits attributes (e.g., windowposition on the web page, size, style, z-order, etc.) as initiallyspecified by the properties of the resource objects 3310.

In one embodiment and with reference to FIG. 34, the browser 2822receives and displays the web page content 3306 within a browser window3402, which includes many possible graphical user interface (“GUI”)elements (e.g., menu 3406, local window 3408, etc.) that form the clientdesktop 3410 displayed on a display device coupled to the client machine10. In this embodiment, the web page content 3306 is displayed within aweb page 3412 displayed in the browser window 3402 and includes one ormore resource icons 3414 and/or one or more resource-output windows3416, which are associated with the resource set 3308. In oneembodiment, one or more of the resource objects 3310 also form part ofthe web page content 3306 of the web page 3412 and can therefore set theinitial attributes (size, z-order, position) of the resource-outputwindows 3416. The initial orientation, size, position, and z-order ofeach of the resource-output windows 3416 displayed on the web page 3412can be modified, as described below, so that the resource-output windows3416 exhibit different orientations, sizes, positions, and z-ordersrelative to the web page 3412 and/or relative to the client desktop3410.

The resource objects 3310 can be any data constructs which indicate tothe browser 2822 displaying the web page content 3306 that aresource-output window 3416 should be displayed at a particular locationin the web page 3412. The resource objects 3310 may include additionalinformation, such as the height, width, border style, background coloror pattern in the resource-output window 3416, along with indicia ofwhich resources 3312 may be displayed in the window 3416, how often theoutput display should be updated, or any other additional informationthat is useful to enhance the display of the resource output.

In one embodiment, the resource objects 3310 are window tags that areembedded in an HTML file, examples of such tags are delineated below.ActiveX tag  <objectclassid=“clsid:238f6f83-b8b4-11cf-8771-00a024541ee3” data=“/ica/direct.ica” CODEBASE=“/cab/wfica.cab”  width=436 height=295> <param name=“Start” value=“Auto”>  <param name=“Border” value=“On”>    </object> Netscape Plugin tag  <embedsrc=“http://www.citrix.com/ica/direct.ica” pluginspage=“http://www.citrix.com/plugin.html”  height=295 width=436Start=Auto Border=On>     <embed> JAVA tag  <applet code=JICA.classwidth=436 height=295>  <param name=Address value=“128.4.1.2602”>  <param name=InitialProgram value=Microsoft Word 7.0>   <paramname=Start value=Auto>   <param name=Border value=On>     </applet>

In each case above, the tag indicates that a resource-output window 3416having a height of 295 pixels and a width of 436 pixels should be drawnto receive output data from the resource 3312. Each tag also specifiesthat the resource 3312 should automatically start execution and that theresource-output window 3416 in which the resource output is displayedshould be drawn with a border. The ActiveX and Netscape Plugin tags havethe properties of the remote resource 3312 specified in the file“direct.ica” located in the directory “/ica.” The JAVA tag specifies theproperties of the remote resource 3312 directly. In the example above,the address of the server 30 hosting the resource 3312 is specified aswell as the name of the resource 3312 to be executed.

In one embodiment, the resource 3312 executes substantially at the sametime as the display of the web page 3412. In another embodiment, theresource 3312 executes when instructed to do so by the server 30 as partof providing web page content 3306 to the web server 3304. In yetanother embodiment, the resource executes in response to a signal, suchas a user-specified input (e.g., selecting a resource icon 3414 on theweb page 3412. Once execution of the resource 3312 is commenced, thebrowser 2822 instantiates a client agent 2814 on the client machine 10.Alternatively, the client agent 2814 is instantiated substantially atthe same time as the display of the web page 3412 or in response touser-specified inputs.

The client agent 2814 comprises one or more software processes, whichexecute on the client machine 10 and which are configured to interactwith the server agent 3316, browser 2822, resource-output window 3416,and/or web server 3304. In one embodiment, the client agent 2814 isspawned as a child process of the browser 2822. In other embodiments,the client agent 2814 is a peer process of the browser 2822 or adynamically linked library associated with the browser 2822. In oneembodiment, a client agent 2814 is instantiated for each resource-outputwindow 3416 displayed in the web page 3412. In another embodiment, asingle client agent 2814 is instantiated for one or more resource-outputwindows 3416 associated with a particular one of the resources 3312 inthe resource set 3308. In yet another embodiment, a single client agent2814 is instantiated for each server agent 3316, which contributed tothe web page content 3306. In yet another embodiment, a single clientagent 2814 is instantiated for the entire resource set 3308.

The browser 2822 passes the properties of the resource objects 3310relating to particular resources 3312 in the resource set 3308 to theclient agent 2814 associated with those same resources 3308.Additionally, the browser 2822 may pass a handle for a resource-outputwindow 3416 to the client agent 2814 or the client agent 2814 may querythe browser 2822 to retrieve the handle for the resource-output window3416. Resource properties, which are not specified by either the browser2822 or the resource objects 3310, may be set to default values. Theclient agent 2814 may also have certain property defaults hard-coded, orthe client agent 2814 may access a file which contains propertydefaults.

The client agent 2814 uses the name of the resource 3312 and the addressof the resource server 30, which are both provided as part of theproperties of the resource objects 3310, to establish a communicationslink and initiate a client-server session with the server agent 3316associated with the resource server 30 and resource 3312. The clientagent 2814 passes some or all of the properties of the resource objects3310 to the server agent 3316 along with any necessary default values.Alternatively, the server agent 3316 may have already received some orall of the properties of the resource objects 3310 from the web server3304 prior to contributing to the web page content 3306, which wassubsequently displayed in the web page 3412. If a particular property isnot passed to the server agent 3316, the server agent 3316 may requestit from the client agent 2814 if it is a necessary property to which ithas no default value (e.g., user ID) or the server agent 3316 mayprovide its own default value for the property (e.g., executionpriority).

The server agent 3316 uses the properties received from the client agent2814 to authenticate the client agent 2814 and to execute the desiredresource 3312 if it has not previously been started. Once the resource3312 is executing and the client agent 2814 has been authenticated, theresource 3312 communicates through the server agent 130 directly withthe client agent 2814, without intervention of the browser 2822 or webserver 3304. The client agent 2814 receives output data from theresource 3312 and displays the output data in the appropriateresource-output window 3416 in the web page 3412. The client agent 2814also detects input events, such as mouse clicks and keyboard inputs,associated with the resource-output window 130 and forwards any suchinput events to the resource 3312 via the server agent 3316. This typeof client-server session is repeated for each resource 3312 in theapplication set 126 that is selected by the user and thus enables theuser to interact with all of the resources in the resource set 3308.

The data exchanged between the client agent 2814 and server agent 3316during the client-server session includes not only input events and thegraphical output data of the resource 3312, but also window attributeinformation (e.g., window position, z-order, size, style, color, etc.).The window attribute information of the resource-output windows 3416 isinitially specified by the resource objects 3310 embedded in the webpage 3412. For example, the resource objects 3310 can include an ActiveXcontrol, which specifies and controls the window attributes of theresource-output windows 3416 during the client-server session. In oneembodiment, the resource-output windows 3416 exhibit the same dimensionsas the corresponding ActiveX controls.

The client agent 2814 communicates the initial window attributes of thelocal application-output windows to the server agent 3316 along withinformation relating to the client desktop 3410 (e.g., size, resolution,etc.). The server agent 3316 responds by conforming the size of itsserver desktop to that of the client desktop 3410 and by conforming thewindow attributes of local server windows to those of theresource-output windows 3416 on the client desktop 3410. Theresource-output windows 3416 on the client desktop 3410 and the serverwindows on the server desktop thus exhibit the same window attributesand display the same graphical output data that is generated by theresource 3312. Note that the server desktop can correspond to either anoffscreen surface contained within the server's video memory or to anonscreen surface displayed on a display device coupled to the server 30.

The user of the client machine 10 can move, resize, and/or alter thez-order or other initial window attributes of the resource-outputwindows 3416 during the client-server session, by entering an inputevent that is detected by the client agent 2814 and then communicated tothe server agent 3316. The server agent 3316 conforms its desktop and/orwindows to be consistent with the input event and then transmits updatedgraphical output data and window attribute information, corresponding tothe input event, to the client agent 2814 with instructions to updatethe resource-output windows 3416 so that they match the windows on theserver 30.

For example, if the user of the client machine 10 resizes one of theresource-output windows 3416 from that originally specified by theresource objects 3310 (such as by clicking with the mouse and draggingthe border of the application-output window 3416 to the desiredlocation/size), the client agent 2814 detects the input event generatedby the mouse action and communicates it to the server agent 3316, whicheffects the same resize event in the on or offscreen surfaces of theserver 30. The server agent 3316 then sends repaint and resizes commandmessages to the client agent 2814 along with updated graphical outputdata and window attribute information. In response, the client agent2814 modifies the appropriate resource object 3310 affected by theresize event (e.g., the ActiveX control discussed above) so that thecorresponding resource-output window 3416 is resized and the updatedgraphical output data is painted within the borders of the -outputwindow 3416.

These embodiments thus enable the window attributes of theresource-output window 3416 to be modified so that the resource-outputwindow 3416 can be moved, resized, etc., within the boundaries of thebrowser window 3402. With reference to FIG. 35 and by way of nonlimitingexample, resource-output window B′ 3502 can be resized using themethodology described above to form resource-output window B″ 3504,which overlaps (thus exhibiting a different z-order from)resource-output window F 3506. Alternatively, the resource-output window3416 can be moved or resized to extend beyond or be entirely outside ofthe browser window 3402. By way of nonlimiting example and withreference to FIG. 36, resource-output window J 3602 lies within theboundaries of the browser window 3402, while resource-output window K3604 extends beyond the boundaries of the browser window 3402 andresource-output window L 3606 is entirely outside the browser window3402. Note that the resource-output windows can exhibit varying z-orderswith respect to other elements in the client desktop 3410. For example,local window 3608 exhibits a z-order between that of the browser window3402 and resource-output window L 3606. In this embodiment, the clientagent 2814 instructs the operating system of the client machine 10 todraw the desired resource-output window 3416 in response to commandmessages received from the server agent 3316, without having to firstmodify the properties of the resource objects 3310 embedded in the webpage 3412, which initially established the window attributes of theresource-output window 3416.

In one embodiment, each input event affecting the resource-output window3416 is transferred to and processed by the server agent 3316, whichthen instructs the client agent 2814 to effect corresponding changes inthe resource-output window 3416. In another embodiment, one or moreinput event types (e.g., click and drag mouse actions directed at movingthe resource-output window 3416 to another grid location on the web page3412) are processed entirely by the client agent 2814 and not reportedto the server agent 3316, where the graphical output data displayedwithin the resource-output window 3416 remains unchanged.

In more detail and with reference to FIG. 37, the client agent 2814comprises a monitor process 3702, a command process 3704, a messagereceiving process 3706, and a message transmission process 3708. In oneembodiment, each process 3702, 3704, 3706, 3708 is a separatelyfunctioning code segment that operates independently of the otherprocesses. For example, the message receiving process 3706 and thecommand process 3704 can be implemented as separate threads, whichcommunicate with each other via a named pipe or shared memory. Use of acommon data set allows the message receiving process 3706 and themessage transmission process 3708 to be synchronized.

The message receiving process 3706 receives graphical data, windowattribute information, and commands from the server agent 3316 via thecommunications link that provides the connectivity between the clientagent 2814 and server agent 3316 during the client-server session. Thecommunications link preferably includes a first virtual channel 3710 anda second virtual channel 3712. Command, event, and window attributeinformation is passed between the client agent 2814 and the server agent3316 via the first virtual channel 3710, while graphical datacorresponding to the graphical contents of the resource-output windows3416 is passed via the second virtual channel 3712. The messagereceiving process 3706 informs the command process 3704 of the commands,window attributes, and graphical data received from the server agent3316 and the command process 3704 further processes this data.

In one embodiment, the command process 3704 processes the commandsreceived from the server agent 3316 by instructing the client operatingsystem 3714 to form and/or modify affected resource-output windows 3416in accordance with the window attributes specified by the server agent3316. The command process 3704 also instructs the client operatingsystem 3714 to display the graphical data provided by the server agent3316 in the appropriate resource-output windows 3416. In one embodiment,the command process 3704 implements changes to the resource-outputwindows 3416 in the client desktop 3410 by issuing GDI commands. Inother embodiments, the command process 3704 issues commands directly toan associated graphics subsystem or via graphics API commands.

The command process 3704 also instructs the monitor process 3702 toperiodically monitor the client desktop 3410 in order to detect changesaffecting the resource-output windows 3416. In one embodiment, themonitor process 3702 instructs the client operating system 3714 toreturn information relating to the client desktop 3410 at predeterminedpolling intervals. In other embodiments, the monitor process 3702monitors the message queue maintained by the client operating system3714 in order to detect changes affecting the resource-output windows.The monitor process 3702 communicates some or all of the detecteddesktop changes to the command process 3704 for further processing.

In one embodiment, the command process 3704 instructs the messagetransmission process 3708 to transmit all of the changes detected by themonitor process 3702 to the server agent 3316 via the first virtualchannel. In another embodiment, the command process 3704 instructs themessage transmission process 3708 to transmit a subset of the detectedchanges, such as changes which only affect the graphical data and/orwindow attributes of the resource-output windows 3416. The server agent3316 receives the detected changes along with any commands from thecommand process 3704 and any input events made by the user of the clientmachine 10 that triggered the detected changes. The server agent 3316then modifies its local desktop to accommodate the detected changes andtransmits associated commands, window attributes, and graphical databack to the client's message receiving process 3706. In this manner,desktop elements, such as the resource-output windows 3416, that arecommon in the client and server desktops remain in lock step.

The command process 3704 of the client agent 2814 ensures thatanalogous/common elements in the client and server desktops remain inlock step by maintaining a common window list. The common window listincludes the window attribute information for each window in the clientdesktop 3410 and for each corresponding window in the resource serverdesktop. In embodiments, in which a plurality of client agents isexecuting on the client machine 10, the command process 3704 of a singleclient agent 2814 has primary responsibility for maintaining the commonwindow list. If the single client agent 2814 terminates, while otherclient agents remain in operation, the remaining client agents willelect another primary client agent to maintain the common window list.

FIG. 38 depicts a system in which a client machine 10 is connected tomore than one remote machine 30, 30′. As shown in FIG. 38, clientmachine 10 has an associated display 3802. The display 3802 may be usedto display one or more components of a graphical user interface, such aswindows and pull-down menus. The collection of graphical user interfacecomponents displayed to a user by the display 3802 is generally referredto as the “desktop.” As shown in FIG. 38, the client machine 10 displaysa local desktop environment 3804 to a user. Client machine 10 mayprovide at least a part of the local desktop environment 3804 or clientmachine 10 may simply display various desktop components received fromother sources such as remote machines 30. As shown in FIG. 38, eachremote machine 30, 30′ has an associated display 3806, 3806′ which alsodisplays a desktop environment 3808, 3808′. It should be noted thatdisplay 3806, 3806′ need not be a video display monitor. For example,display 3806, 3806′ may simply be a bank of video RAM to which resourceswrite the output of graphical procedure calls. FIG. 38 depicts anembodiment of a system in which each machine 30 displays 3806, 3806′displays one graphical user interface window 3810, 3812′.

Each remote machine 30, 30′ also includes at least one agent 3814,3814′. In some embodiments, each remote machine 30, 30′ includes oneagent 3814, 3814′ for each client machine 10 connected to the remotemachine 30, 30′. Client machine 10 may also host an agent 3816. In someembodiments, a client machine 10 hosts a separate local agent 3816 foreach remote machine 30 to which the client machine 10 is connected. Inother embodiments, the client machine 10 hosts a single agent 3816 thatmanages connections to multiple remote machines 30. Each of the agents3814, 3814′, 3816 may monitor their associated desktop environment 3808,3808′, 3816 for windows which: change position; are opened; are closed;change size; are minimized; are maximized; or are brought to the top ofthe desktop, i.e., windows which gain focus that do not previously havefocus. Each agent 3814, 3814′, 3816 transmits messages indicative ofchanges in their associated desktop 3808, 3808′, 3804 to other agents.For example, local agent 3816 may receive messages transmitted fromserver node agents 3814, 3814′. The local agent 3816 commands the clientmachine 10 to modify the local desktop environment 3804 in response tothe messages received from server agents 3814, 3814′, that is, the localagent 3816 issues commands to the client machine 10 to conform the localdesktop environment 3804 to the desktop environment 3804 In otherembodiments, agents 3814, 3814′ for remote machine 30, 30′ receivemessages from a local agent 3816 and command the machine 30, 30′ tomodify the desktop environment 3808, 3808′ in response to messagesreceived from the local agent 3816.

In one embodiment, the agents 3814, 3816 monitor changes to theirassociated desktop environment 3808, 3808′ by periodically issuing oneor more of a set of commands provided by the operating system that allowdetails of the graphical user interface desktop to be determined. Forembodiments in which the agents 3814, 3816 reside on nodes that executea version of the WINDOWS operating system, the agents 3814, 3816 mayperiodically issue the Enum Windows command to the WINDOWS operatingsystem, which returns a list of all windows present on the desktop,together with information related to those windows. The agents 3814,3816 can issue the Enum Windows command every 50 milliseconds, every 100milliseconds, every 500 milliseconds, or at any period that allows theagent 3814, 3816 to rapidly determine when changes to its associateddesktop environment have occurred without putting a significantcomputational burden on the node. In this embodiment, the agent 3814,3816 maintains a data structure storing information about the desktopwindows and compares the values returned by the Enum Windows command tothe data structure to determine changes.

Information determined and stored by the agent 3814, 3814′ can includethe title bar associated with each window, the location of each windowin the desktop environment 3808, 3808′, the size of each window, and thez-order positioning of each window in the desktop environment 3808,3808′. In another embodiment, the agent 3814, 3814′, 3816 monitors anintranode graphics message queue to determine changes to its associateddesktop environment. Server agents 3814, 3814′ monitor an intraservermessage queue and local agent 3816 monitors an intraclient messagequeue. In this embodiment, changes to the desktop environment 3808,3808′ are affected via messages sent to a graphics subsystem from systemapplications or the operating system itself. Thus, a resource executingon a remote machine 30, 30′ would send a message to a graphics engineresiding on the server 30, 30′ in order to change the server desktopenvironment 3808, 3808′. Other commands which return graphical userinterface data are readily apparent to those of ordinary skill in theart. For embodiments in which the agents 3814, 3816 reside on nodesexecuting a version of the WINDOWS operating system, the agents 3814,3816 monitor the Windows Message Queue for messages affecting thedesktop environment associated with the node on which the agent resides.Examples of such messages include: WM_SETFOCUS, which indicates to whichwindow focus will be given (i.e., brought to the “top” of the desktop);WM_KILLFOCUS, which removes focus from an indicated window; andWM_WINDOWPOSCHANGING, which indicates a change in the position of awindow. Other messages that can be posted to the Windows Message Queueare readily known to those of ordinary skill in the art.

Referring now to FIG. 39, the steps taken during a server-initiatedevent are shown. The agent 3814 for remote machine 30 senses a change inits associated desktop (step 3902). The agent 3814 may do this byintercepting a window event on the server message queue, or the agent3814 may determine a change in the desktop by comparing the resultsreturned from serially issued operating system commands, as describedabove. The agent 3814 sends a message to a client agent 3816 indicatingthe change in the server desktop 3810 (step 3904). For example, if a newwindow has been given focus, the agent 3814 can transmit a message to aclient agent 3816 indicating the identity of the new “top” window. Inone embodiment, the agent 3814 broadcasts its message to all clientagents 3816 that exist in the system. Alternatively, the agent 3814 maytransmit its message only to a predetermined subset of client agents3816. For example, when a client machine 10 makes a connection to aremote machine 30, the client agent 3816 may register with the agent3814. In this embodiment, the agent 3814 would transmit change messagesonly to those client agents that have registered with the remote machine30.

The client agent 3816 receives the transmitted message (step 3906). Inembodiments in which the remote machine 30 broadcasts commands, theclient agent 3816 must have some mechanism for determining whether atransmitted command affects its associated desktop. For example, theclient agent 3816 may maintain a list of remote machines 30 to which itis connected. In these embodiments, the client agent 3816 responds tomessages broadcast by any remote machine 30 present in its list. Forembodiments in which the agent 3814 does not broadcast messages, no suchmechanism is necessary.

The client agent 3816 implements a change to its associated desktop 14responsively to the received message (step 3908). The client agent 3816may accomplish this by directly issuing graphics Application ProgrammingInterface commands that cause the client machine 10 to change thedisplay of its associated desktop. Alternatively, the client agent 3816may issue GDI commands to change its associated desktop. In still otherembodiments, the client agent 3816 issues commands directly to thesystem, whether implemented in hardware or software, responsible fordisplaying graphics on the client machine 10.

Referring now to FIG. 40, the steps taken when a client machine 10initiates a desktop change are shown. The client agent 3816 senses achange in its associated desktop 14 (step 4002). As noted above, thismay be done on an event-driven basis or by polling the operating systemoperating on the client machine 10. The client agent 3816 determines towhich remote machine 30 the affected window belongs (step 4004). Tofacilitate this process, the client agent 3816 may maintain a list thatassociates remote windows with a particular remote machine 30. Theclient agent 3816 then sends a message to the identified remote machine30 indicating the change in its desktop 14 (step 4006). Alternatively,the client agent 3816 may skip step 404 entirely and broadcast itschange message to all remote machines 30. The server agent receives thetransmitted message (step 4008) and implements the change in itsassociated desktop (step 4010), as described above.

In one particular embodiment, a client machine 10 and a remote machine30 communicate using the ICA protocol and the client machine 10 and theremote machine 30 execute a version of the WINDOWS operating system.Client machine 10 hosts a local agent 3816 that may be provided as adynamically linked library module. The remote machine 30 hosts an agent3814 that may be provided as a separate thread.

In this embodiment, the local agent 3816 and the agent 3814 exchangegraphical data, i.e., the data actually displayed in each window on thedesktop, via a first ICA virtual channel. Information about windowpositioning, window size, z-access ordering of window and other suchinformation is communicated between the client machine 10 and the remotemachine 30 via a second ICA virtual channel. Throughout the description,when the client machine 10 and the remote machine 30 are activelyexchanging information via the second ICA virtual channel, the clientmachine 10 will be referred to as being in “seamless windowing mode.”

Referring now to FIG. 41, the process for enabling seamless windowingmode between the local agent 3816 and agent 3814 is shown. In thisembodiment, all communication between a server agent and a client agentis packet-oriented and takes place over a dedicated ICA virtual channel,making the functioning of the agents 3814, 3816 independent from theunderlying communication protocol. All packets start with packet type (1byte), followed by packet data length (2 bytes, can be zero) and data(optional). Agents 3814, 3816 will try to send as much data in a singlenetwork packet as possible, but it will always send complete packets.That is, the size of seamless window virtual packets never exceeds theallowable size of an ICA packet. Packet flow control and deliveryconfirmation is implemented by the transport level of the ICA protocol.Individual packets are executed immediately on reception.

The client agent 3816 waits for an initial packet from the server agent3814. After user logon to the server, a server agent 3814 will beinvoked (step 4104).

The server agent 3814 sends a TWI_PACKET_START packet to the clientagent 3816, which includes some essential information about the remotemachine 30 desktop environment (desktop resolution, desktop size,version number of ICA protocol supported by the server, etc.) (step4106). This packet is sent by the server agent 3814 on initialconnection or on reconnect, and is used to: (1) detect seamlesswindowing capabilities of the client machine 10; and (2) requests basicmachine 10 information.

The client agent receives the TWI_PACKET_START packet (step 4107) andresponds with a TWI_PACKET_C2H_START_ACK packet, confirmingTWI_PACKET_START and supplying machine 10 version/capabilitiesinformation (step 4108). This packet is sent by the client agent 3816 toconfirm reception of TWI_PACKET_START packet and to send the requestedbasic machine 10 information to the server agent 3814.

If there is no response from the client agent 3816 (step 4109), theserver agent 3814 assumes that the client machine 10 is unable to enterseamless windowing mode, and the seamless windowing virtual channel isnot used by the remote machine 30 to communicate window information. Inthis case, the remote machine 30 continues to communicate graphical datato the client machine 10 via another virtual channel, and the clientmachine 10 desktop displays the server desktop without incorporatingwindows from other nodes.

The client agent 3816 uses the information sent by the server agent 3814in step 4106 to determine if a seamless windowing session can beestablished between the server agent 3814 and the client agent 3816. Inone embodiment, the client agent 3816 compares information relating tothe version of the virtual channel protocol supported by the serveragent 3814 to makes the determination If the client agent 3816determines that it is possible to enable seamless windowing mode (step4110), the client agent 3816 sends a TWI_PACKET_C2H_OPEN packet to theserver agent 3814 (step 4111). This packet requests that the serveragent 3814 enable seamless windowing mode.

On reception of a TWI_PACKET_C2H_OPEN packet (step 4112) the serveragent 3816 (I) resets its internal data structures, (ii) sends aTWI_PACKET_SYSINFO packet to the client agent 3816 to communicate somegeneral information regarding the window settings on the remote machine30 to the client agent 3816, (iii) sends a TWI_PACKET_OPEN packet to theclient agent 3816 (step 4114) indicating the establishment of seamlesswindowing mode, and (iv) enables its main polling loop (step 4116) thatwill poll the operating system on the server node for desktop changes.If the client agent 3816 and the server agent 3814 do not support thesame version of the seamless window protocol, the server agent 3814ignores the TWI_PACKET_C2H_OPEN packet.

On reception of TWI_PACKET_OPEN packet (step 4120), the client agent3816 resets its internal data structures (step 4122) and seamlesswindowing mode between the client agent 3816 and the server agent 3814is established.

During a seamless windowing mode session, the server agent 3814 willsend window information such as window position, size, styles, windowtext, etc. for all top-level windows on the server node. Also,foreground window information is sent, i.e., which window on the servernode desktop is the foreground window. In accordance with thisinformation, the client agent 3816 creates windows with the samesize/position as the server node windows on the machine desktop. In someembodiments, window elements are transmitted as bitmaps from the servernode 20. Examples of packets sent by the server agent 3814 include:TWI_PACKET_CLOSE, which is sent to switch the client agent 3816 out ofseamless windowing mode and back to regular, or full screen, mode; thatis, the client machine 10 is switched back to displaying the server nodedesktop environment without incorporating windows from other desktopenvironments; TWI_PACKET_CREATEW, which is sent to create new windows onthe client machine 10; TWI_PACKET_DELETEW, which is sent to destroy awindow on the client machine 10; TWI_PACKET_CHANGEW, which is sent tochange a window displayed by the local node 10; TWI_PACKET_SYSINFO,which is sent to report remote machine 30 system settings—normally it issent only once, but the packet can be sent multiple times;TWI_PACKET_FOREGROUNDW, which is sent during normal seamless windowingmode operation to change the foreground window; TWI_PACKET_SETTOPW,which is sent during normal seamless windowing mode operation to changethe top window, that is, to bring a new window to top;TWI_PACKET_SETFOCUS, which is sent during normal seamless windowing modeoperation to change the focus window; TWI_PACKET_FOCUSACK, which is sentin response to TWI_PACKET_C2H_SETFOCUS (see below), and reports theresult of a SetFocus attempt; and TWI_PACKET_SPA_STATUS, which is sentin response to TWI_PACKET_C2H_START_PUBLICAPP (see below), and is usedto report the result of the requested operation.

Examples of packets that can be sent by the client agent 3816 to theserver agent 3814 include: TWI_PACKET_C2H_PAUSE, which is sent tosuspend the server agent 3814, that is, the server agent 3814 will stopsending window information, clear its internal data structure and send aTWI_PACKET_CLOSE packet (see above); TWI_PACKET_C2H_RESUME, which issent to resume the server agent 3814—the server agent 3814 will clearits internal data structure, and send a TWI_PACKET_OPEN packet (seeabove); TWI_PACKET_C2H_SETPOS, which is sent to report windowsize/position change on the machine; TWI_PACKET_C2H_SETFOCUS, which issent to report a change in the focus window on the machine;TWI_PACKET_C2H_RESTORE, which is sent to request restoration of aminimized window; TWI_PACKET_C2H_TERMINATE, which is sent to requesttermination of a program executing on the remote machine 30;TWI_PACKET_C2H_STARTAPP, which is sent to start a new resource on theremote machine 30; TWI_PACKET_C2H_LOGOUT, which is sent to end thecurrent session; TWI_PACKET_C2H_START_PUBLICAPP, which is sent to starta new published resource on the remote machine 30; andTWI_PACKET_C2H_CLIENTINFO, which is sent to report client desktopsettings to the server agent 3814—this packet is generally sent onstartup, but can also be used during seamless windowing session.

The client agent 3816 will try to perform some operations (such aswindow move and resize) locally, sending update information back to theremote machine 30 afterwards. Proper window behavior is emulated byintercepting the WM_NCHITTEST message for the client-created windows.

Foreground window changes can happen on both the client machine 10 andthe remote machine 30, so the client machine 10 and remote machine 30will negotiate and balance actual foreground window changes. Forexample, if the remote machine 30 changes its foreground window, thatchange should be properly represented on the client machine 10 desktop.The server agent 3814 sends information regarding the new foregroundwindow to the client agent 3816 using the TWI_PACKET_FOREGROUNDW packet.Similarly, if the client agent 3816 detects a foreground window changeon the client machine 10 desktop, the client agent 3816 sendsinformation regarding the change to the server agent 3814 and the serveragent 3814 implements the change on the remote machine 30 desktop.

When focus is taken away from a window representing a server window andis given to a local machine 10 window, the client machine 10 notifiesthe remote machine 30 of the change and the remote machine 30 givesfocus to an invisible window. For embodiments in which the clientmachine 10 is connected to two server nodes 30, and focus is shiftedfrom a window representing a window from the first remote machine 30 andis given to a window representing a window from the second remotemachine 30′, the client machine 10 sends a packet informing the currentremote machine 30 or 30′ that its window no longer has focus. Once theremote machine 30 or 30′ responds by giving focus to an invisiblewindow, the client agent 3816 instructs the other remote machine 30 thatits window now has focus on the client machine 10 desktop.

In some embodiments, it is desirable to add some complexity to theagent's main polling loop to reduce network traffic. In theseembodiments, the main polling loop includes a comparison between thecurrent foreground window and the identity of the window last requestedto be moved to the foreground. If the current foreground window matchesthe window identified in the most recent request, the agent does notneed to send information acknowledging the change. This technique isuseful in both server agent 3814 and client agents 3816.

Window z-ordering on the client machine 10 is a superset of the servernode z-ordering (machine 10 will always have more windows than thehost). Server node Bordering is reproduced on the client machine 10 byreproducing owner/owned relationship among windows and the TOP_MOST flagin the window style. Owner/owned relationships refer to windows whichare children of other windows, such as dialog boxes associated withresource windows. The dialog box is said to be owned by the resourcewindow, and the dialog box will always appear on top of its owner. TheTOP_MOST flag indicates that a particular window should appear on “top”of the desktop, for example, the status bar in WINDOWS 95.

When a user disconnects, the server agent 3814 switches itself tosuspended mode, and will not send information to the client agent 3816.On a reconnect, the server agent 3814 sends a TWI_PACKET_START packet,reporting HostAgentState as “already running, reconnect.”

Based on the version number of the protocol supported by the server theclient machine 10 will decide whether it is possible to enable seamlesswindowing mode (from the client machine 10 point of view). If it ispossible to switch to seamless windowing mode, the client agent 3816will send a TWI_PACKET_C2H_OPEN packet, asking the server agent 3814 toenable seamless windowing mode.

Each agent responsible for monitoring an associated desktop may beimplemented as a stand-alone software routine (such as an executablefile on DOS-based systems), a dynamically linked library routine (DLL),or as an integral piece of the operating system. Referring now to FIG.42, and in brief overview, each agent includes a message receivingfacility 4202, a command facility 4204, a monitor facility 4206, and amessage transmission facility 4208. Agent-agent communication isfull-duplex, i.e., agents can transmit and receive messagessimultaneously. Thus, each facility can be implemented as a separatelyfunctioning code segment that operates independently of the otherfacilities. For example, message receiving facility 4202 and commandfacility 4204 can be implemented as separate threads which communicatewith each other via a named pipe or shared memory. Use of a common dataallows the message receiving facility 4202 and the message transmittingfacility 4208 to be synchronized.

Message receiving facility 4202 receives messages transmitted from otheragents indicating changes in the desktop environments associated withthose agents. Message receiving facility 4202 may connect directly withthe physical layer of the communications protocol the agents use tocommunicate, or the message receiving facility 4202 may operate at ahigher layer of the protocol by cooperating with one or morecommunications subsystems. For embodiments in which messages arebroadcast by agents, the message receiving facility 4202 has somemechanism for determining whether a broadcast message is intended forit. For example, the message receiving facility 4202 may store a list ofthe windows which its associated desktop displays. The message receivingfacility 4202 would compare the target of any received message to itslist of windows to determine whether or not to take action on thereceived message. The message receiving facility may be implemented as ablocking function. Alternatively, the message receiving facility can beimplemented a call-back function invoked by the ICA virtual channeltransport.

Once the message receiving facility 4202 has determined that a receivedmessage is intended for its desktop, the command facility is invoked toeffect the change indicated by the message to the associated desktopenvironment. The command facility 4204 may be passed the receivedmessage facility, or the message receiving facility 4202 may process thereceived message before communicating with the command facility 4204.The command facility 4204 may implement the desktop change indicated bythe received message by issuing GDI commands. In other embodiments, thecommand facility 4204 may issue commands directly to an associatedgraphics subsystem or may issue other graphics API commands.

During a seamless windowing session, a number of desktops are associatedwith a single machine 10—one desktop on the client machine 10 itself andone desktop per remote machine 30 to which the client machine 10 isconnected. The client agent 3816, in conjunction with the server agent3814, 3814′, creates a combined window list representing the z-order ofall desktops. All participating desktops are “linked” together by theclient agents 40 and the server agents 3814, 3814′, and any z-orderchanges on any desktops will be propagated to other desktops.

In one embodiment, each remote machine 30 has knowledge only of its owngraphical desktop representation and the remote machine 30 desktops areindividually represented within the client machine 10. The clientmachine 10 display is updated by combining all remote machine 30 andmachine 10 desktop images into a single display image based on thewindow information that has been obtained from each server node 30 30′by the client agent 3816. The resulting image is displayed at the clientmachine 10.

The combining process involves building a common window list based onthe windows information exchanged by all agents. Using the combinedwindow list, the graphical desktop data is clipped and merged forrepresentation by the client machine 10. The node takes care of“clipping” displayed windows resulting from the commands issued by thecommand facility 4204. Such “clipping” functions are well-known to thoseof ordinary skill in the art. In some embodiments, however, the commandfacility 4204 maintains a shadow bitmap of clipped windows. That is, thecommand facility 4204 maintains a bit image of windows that are obscuredby other windows. This allows the agent to change its associated desktopwithout requiring it to reload the window image of an obscured windowfrom the appropriate source. In other embodiments, the node determineswhether graphical data is obscured at the time it is received. If it is,the node ignores the received graphical data. If it is not, the nodedisplays the data. The node makes a determination as to whether thegraphical data is obscured by applying clipping functions.

Monitoring facility 4206 monitors the desktop associated with the agent.Monitoring facility 4206 may monitor the desktop by periodically issuingcommands provided by the operating system executing on the node whichreturn information about the node's desktop. Alternatively, themonitoring facility 506 may watch for messages posted to an intranodemessage queue. As noted above, in one particular embodiment themonitoring facility 4206 monitors the Windows Message Queue. Once adesktop change occurred, the message transmission facility 4208transmits a message indicating the change that has occurred. In someembodiments, the message transmission facility 4208 broadcastsnotification of the change.

In one embodiment, message transmission facility 4208 can be implementedin the form of non-blocking function that can be called from any windowprocedure. If the function can not send a data packet immediately (forexample, the communication subsystem has no buffer space), a timer willbe set and retry attempts will be done until the send succeeds.

Referring now to FIG. 43, an embodiment of a system for enablingseamless windowing mode between a client machine 10 and remote computingenvironments is shown. In brief overview, the system includes a firstvirtual channel 4302, a first remote desktop environment 4304, a nativeoperating system 4306, a remote window 4308, a second virtual channel4310, a third virtual channel 4312, a second remote desktop environment4314, a virtualized operating system 4316, a remote window 4318, afourth virtual channel 4320, a local agent 4330, and a local desktopenvironment 4340.

In some embodiments the methods and systems described above inconnection with FIGS. 24-37 may be implemented in systems includingvirtual machines. In some embodiments, the local agent 4330 resides on aclient machine 10. In one of these embodiments, the client machine 10establishes a connection to a physical machine providing access to aresource requested by the client machine 10. In this embodiment, thelocal agent 4330 on the client machine 10 may receive window attributedata and graphical data associated with a remote window 4308 from anagent on a remote machine 30 as described above.

In other embodiments, the client machine 10 has established a connectionto a virtual machine providing access to a resource. In one of theseembodiments, an agent for the remote machine 30 may reside in thevirtual machine. In another of these embodiments, the agent for theremote machine 30 may reside in a hypervisor into which the virtualmachine is launched. In still another of these embodiments, the agentfor the remote machine 30 may reside in a second virtual machineproviding management functionality for the virtual machine on the remotemachine 30. In these embodiments, the client machine 10 may receivewindow attribute data and graphical data associated with a remote window4308 through the implementation of the methods and systems describedabove in connection with FIGS. 24-37.

The client machine 10 may access multiple resources from differentremote machines 30. In some embodiments, the client machine 10 mayaccess resources on different machines substantially simultaneously overmultiple established connections to, for example, both physical machineson remote machines 30 and to virtual machines executing in a hypervisoron remote machines 30′.

Referring still to FIG. 43, and in greater detail, a block diagramdepicts one embodiment of a system for receiving window attribute dataand graphical data associated with remote windows from virtualizedoperating systems and from native operating systems. The first virtualchannel 4302 is coupled to the first remote desktop environment 4304,which is provided by the native operating system 4306. The first virtualchannel 4302 conveys graphical data associated with the remote window4308 provided by the first remote desktop environment 4304. The secondvirtual channel 4310 coupled to the first remote desktop environment4304 conveys window attribute data associated with the remote window4308 provided by the first remote desktop environment 4304.

The third virtual channel 4312 is coupled to the second remote desktopenvironment 4314 provided by a virtualized operating system 4316, thethird virtual channel 4312 conveying graphical data associated with thesecond remote window 4318 provided by the third remote desktopenvironment 4314. The fourth virtual channel 4320 coupled to the secondremote desktop environment 4314 and conveying window attribute dataassociated with the second remote window 4318 provided by the secondremote desktop environment 4314. In one embodiment, the window attributedata associated with the remote windows 708 and 718 and conveyed by thesecond virtual channel 4310 and the fourth virtual channel 4320 includesthe size and z-order of the remote windows.

The local agent 3814, coupled to the first remote desktop 4304 and thesecond remote desktop 4314 via the first, second, third and fourthvirtual channels directs the formation of a first window in the localdesktop environment 4340 corresponding to the remote window 4308provided by the first remote desktop environment 4304 and the formationof a second window in the local desktop environment 4340 correspondingto the second remote window 4318 provided by the second remote desktopenvironment 4314. The first local window displays the graphical dataconveyed by the first virtual channel 4302 in accordance with the windowattribute data conveyed by the second virtual channel 4310 and thesecond local window displaying the graphical data conveyed by the thirdvirtual channel 4312 in accordance with the window attribute dataconveyed by the fourth virtual channel 4320. In one embodiment, thelocal agent 4330 forms and maintains a combined windows listrepresenting a modifiable z-order of a corresponding window in the localdesktop environment 4340.

In some embodiments, a local operating system forms the local desktopenvironment 4340. In one of these embodiments, the local agent 4330periodically polls the local operating system to detect an attributechange in one of the first local window and the second local window. Inanother of these embodiments, upon detection of attribute change, thelocal agent 4330 transmits a message to one of the first remote desktopenvironment and the second remote desktop environment indicative of theattribute change. In some embodiments, corresponding windows on thelocal desktop environment 4340 and on the remote desktop environments4304 and 4314 exhibit window attribute data substantially similarrelative to the local desktop environment as to the window attributedata of the remote windows relative to their respective remote desktopenvironment.

Referring now to FIG. 44, a flow diagram depicts one embodiment of thesteps taken in a method of receiving window attribute data and graphicaldata associated with remote windows from virtualized operating systemsand from native operating systems. In brief overview, graphical dataassociated with a remote window provided by a first remote desktopenvironment provided by a native operating system is received via afirst virtual channel coupled to the remote desktop (step 4302). Windowattribute data associated with the remote window provided by the firstremote desktop environment is received via a second virtual channelcoupled to the first remote desktop environment (step 4304). Graphicaldata associated with a remote window provided by a second remote desktopenvironment provided by a virtualized operating system is received via athird virtual channel coupled to the remote desktop environment (step4306). Window attribute data associated with the remote window providedby the second remote desktop environment is received via a fourthvirtual channel coupled to the second remote desktop environment (step4308). A first window is formed in the local desktop environment, thefirst window displaying the graphical data received from the firstvirtual channel in accordance with the window attribute data receivedfrom the second virtual channel (step 4310). A second window is formedin the local desktop environment, the second window displaying thegraphical data received from the third virtual channel in accordancewith the window attribute data received from the fourth virtual channel(step 4312).

In some embodiments, a combined windows list is formed and stores atleast some of the window attribute data. In other embodiments, a localoperating system associated with the local desktop environment is polledto detect an attribute change in one of the first local window and thesecond local window and transmitting a message to one of the firstremote desktop environment and the second remote desktop environmentindicative of the detected attribute change. In still other embodiments,the local windows exhibit window attribute data substantially similarrelative to the local desktop environment as the window attribute dataof the remote windows relative to the remote desktop environments.

Referring to FIG. 45, one embodiment of a system for providing a clientwith a reliable connection to a host service is shown. In a broadoverview, a system 4500 for network communications includes a clientmachine 10 (e.g., a first computing device) in communication with afirst protocol service 4502 (e.g., a second computing device) over anetwork 150. Also included in the system 4500 are a plurality of hostservices 4516 a-4516 n (e.g., third computing devices) that are incommunication, over a network 150′, with the first protocol service 4502and, through the first protocol service 4502 and over the network 150,with the client machine 10. Alternatively, in another embodiment, andwith reference now to FIG. 46, the first protocol service 4502 and thehost services 4516 a-4516 n are not implemented as separate computingdevices, as shown in FIG. 45, but, rather, they are incorporated intothe same computing device, such as, for example, a remote machine 30.The system 4500 can include one, two, or any number of remote machines30, 30′. The protocol service 4502 may also be provided as a remotemachine 30.

In one embodiment, the networks 150 and 150′ are separate networks, asin FIG. 45. The networks 150 and 150′ can be the same network 150, asshown in FIG. 46.

Referring still to the embodiments of FIGS. 45 and 46, the clientmachine 10 is configured to establish a connection 4504 between theclient machine 10 and a first protocol service 4502 over the network 150using a first protocol. For its part, the first protocol service 4502 isconfigured to accept the connection 4504. The client machine 10 and thefirst protocol service 4502 can, therefore, communicate with one anotherusing the first protocol as described below in reference to FIGS. 47-48and FIG. 49.

In some embodiments, as shown in FIGS. 45 and 46, a client agent 4506 isincluded within the client machine 10. The client agent 4506 can be, forexample, implemented as a software program and/or as a hardware device,such as, for example, an ASIC or an FPGA. The client agent 4506 can useany type of protocol and it can be, for example, an HTTP client agent,an FTP client agent, an Oscar client agent, a Telnet client agent, anIndependent Computing Architecture (ICA) client agent from CitrixSystems, Inc. of Fort Lauderdale, Fla., or a Remote Desktop Procedure(RDP) client agent from Microsoft Corporation of Redmond, Washington. Insome embodiments, the client agent 4506 is itself configured tocommunicate using the first protocol. In some embodiments (not shown),the client machine 10 includes a plurality of client agents 4506 a-4506n, each of which communicates with a host service 4516 a-4516 n,respectively.

In another embodiment, a standalone client agent is configured to enablethe client machine 10 to communicate using the first protocol. Thestandalone client agent can be incorporated within the client machine 10or, alternatively, the standalone client agent can be separate from theclient machine 10. The standalone client agent is, for example, a localhost proxy. In general, the standalone client agent can implement any ofthe functions described herein with respect to the client agent 4506.

As also described further below, the first protocol service 4502 is, inone embodiment, itself configured to communicate using the firstprotocol. The first protocol service 4502 is configured to establish aconnection 4508 a-4508 n between the first protocol service 4502 and thehost service 4516 a-4516 n, respectively. For example, the firstprotocol service 4502 can establish a connection 4508 a between thefirst protocol service 4502 and one host service 4516 a and a connection4508 b between the first protocol service 4502 and another host service4516 b. In one embodiment, the first protocol service 108 separatelyestablishes such connections 4508 a-4508 n (i.e., the first protocolservice 4502 establishes one connection at a time). In anotherembodiment, the first protocol service 4502 simultaneously establishestwo or more of such connections 4508 a-4508 n.

In yet another embodiment, the first protocol service 4502 canconcurrently establish and maintain multiple connections 4508 a-4508 n.The first protocol service 4502 is configured to provide two or moreconnections 4508 a-4508 n without interrupting the connection 4504 withthe client machine 10. For example, the first protocol service 4502 canbe configured to establish the connection 4508 a between the firstprotocol service 4502 and the host service 4516 a when a user of theclient machine 10 requests execution of a first application programresiding on the host service 4516 a. When the user ends execution of thefirst application program and initiates execution of a secondapplication program residing, for example, on the host service 4516 b,the first protocol service 4502 is, in one embodiment, configured tointerrupt the connection 4508 a and establish the connection 4508 bbetween the first protocol service 4502 and the host service 4516 b,without disrupting the connection 4504 between the first protocolservice 4502 and the client machine 10.

The first protocol service 4502 and the host services 4516 a-4516 n cancommunicate over the connections 4508 a-4508 n, respectively, using anyone of a variety of secondary protocols, including, but not limited to,HTTP, FTP, Oscar, Telnet, the ICA remote display protocol from CitrixSystems, Inc. of Fort Lauderdale, Fla., and/or the RDP remote displayprotocol from Microsoft Corporation of Redmond, Wash. For example, thefirst protocol service 4502 and the host service 4516 a can communicateover the connection 4508 a using the ICA remote display protocol, whilethe first protocol service 4502 and the host service 4516 b cancommunicate over the connection 4508 b using the RDP remote displayprotocol.

In one embodiment, the secondary protocol used for communicating betweenthe first protocol service 4502 and a host service 4516, such as, forexample, the ICA remote display protocol, includes a plurality ofvirtual channels. A virtual channel is a session-oriented transmissionconnection that is used by application-layer code to issue commands forexchanging data. For example, each of the plurality of virtual channelscan include a plurality of protocol packets that enable functionality atthe remote client machine 10. In one embodiment, one of the plurality ofvirtual channels includes protocol packets for transmitting graphicalscreen commands from a host service 4516, through the first protocolservice 4502, to the client machine 10, for causing the client machine10 to display a graphical user interface. In another embodiment, one ofthe plurality of virtual channels includes protocol packets fortransmitting printer commands from a host service 4516, through thefirst protocol service 4502, to the client machine 10, for causing adocument to be printed at the client machine 10.

In another embodiment, the first protocol is a tunneling protocol. Thefirst protocol service 4502 encapsulates a plurality of secondaryprotocols, each used for communication between one of the host services4516 a-4516 n and the first protocol service 4502, within the firstprotocol. As such, the host services 4516 a-4516 n and the firstprotocol service 4502 communicate with the client machine 10 via theplurality of secondary protocols. In one embodiment, the first protocolis, for example, an application-level transport protocol, capable oftunneling the multiple secondary protocols over a TCP/IP connection.

Referring to FIG. 47, communications between the client machine 10 andthe first protocol service 4502 via the connection 4504 take the form ofa plurality of secondary protocols 4702 a-4702 n (e.g., HTTP, FTP,Oscar, Telnet, ICA, and/or RDP) encapsulated within a first protocol4704. This is indicated by the location of secondary protocols 4702a-4702 n inside the first protocol 4704. Where secure communication isnot called for, the first protocol 4704 can be, as illustrated in FIG.47, communicated over an unsecured TCP/IP connection 4706.

Referring now to FIG. 48, if secure communication is used, the firstprotocol 4704 is communicated over an encrypted connection, such as, forexample, a TCP/IP connection 4802 secured by using a secure protocol4804 such as the Secure Socket Layer (SSL). SSL is a secure protocolfirst developed by Netscape Communication Corporation of Mountain View,Calif., and is now a standard promulgated by the Internet EngineeringTask Force (IETF) as the Transport Layer Security (TLS) protocol anddescribed in IETF RFC-2246.

Thus, the plurality of secondary protocols 4702 a-4702 n arecommunicated within the first protocol 4704 with (FIG. 48) or without(FIG. 47) a secure protocol 4804 over the connection 4504. The secondaryprotocols that can be used to communicate over the connections 4508a-4508 n include, but are not limited to, HTTP, FTP, Oscar, Telnet, ICA,and RDP. Moreover, in one embodiment, at least one of the secondaryprotocols, as described above, includes a plurality of virtual channels,each of which can include a plurality of protocol packets enablingfunctionality at the remote client machine 10. For example, in oneembodiment, one host service 4516 a is a web server, communicating withthe first protocol service 4502 over the connection 4508 a using theHTTP protocol, and another host service 4516 b is an application server,communicating with the first protocol service 4502 over the connection4508 b using the ICA protocol. The host service 4516 b generates bothprotocol packets for transmitting graphical screen commands to theclient machine 10, for causing the client machine 10 to display agraphical user interface, and protocol packets for transmitting printercommands to the client machine 10, for causing a document to be printedat the client machine 10.

In another embodiment, the method and systems described herein reducethe number of times network connections are opened and closed. In oneembodiment, the first protocol 4704 allows the secondary protocolconnections 4702 a-4702 n tunneled therein, such as, for example, anHTTP connection 4702 n, to be opened and/or closed, repetitively,without also requiring the transport connection over which the firstprotocol 4704 is communicated (e.g., TCP connection 4706 and/or 4802),the secure protocol connection 4804, or the first protocol connection4704 itself to similarly be repetitively opened and/or closed. Withoutthe encapsulation of the first protocol 4704, the secondary protocol4702 a-4702 n may frequently open and close network connections, such asTCP connections. This would add significant delays and overhead to thesystem. These delays and overhead would be further increased by the useof a secure encapsulation protocol 4806, such as SSL, which havesignificant overhead in establishing network connections. Byencapsulating the secondary protocol 4702 a-4702 n within the firstprotocol 4704 and maintaining the connection of the transport connection(4706, 4802), the secondary protocols 4702 a-4702 n, as part of thepayload of the first protocol 4704, do not need to perform frequent andcostly open and closes of the network connection 4504. Furthermore,since the secondary protocols 4702 a-4702 n can be communicated withinthe first protocol 4704 with a secure protocol 4804, the secondaryprotocols 4702 a-4702 n also do not need to open and close securedconnections such as with SSL. The transport connection (4706, 4802)establishes and maintains the network connection 4504 so that theencapsulated second protocols 4702 a-4702 n can be communicated withoutrepetitively opening and closing the secured or unsecured networkconnection 4504. This significantly increases the speed of operation incommunicating the secondary protocols 4702 a-4702 n.

As described above, the secondary protocols 4702 a-4702 n carry protocolpackets related to applications using such protocols as HTTP, FTP,Oscar, Telnet, RDA or ICA. The secondary protocol packets 4902 a-4902 ntransport data related to the application functionality transactedbetween the client machine 10 and the host service 4516 a-4516 n. Forexample, a user on the client machine 10 may interact with a web pageprovided by a host service 4516 a-4516 n. In transactions between theclient machine 10 and the host service 4516 a-4516 n, the secondaryprotocol 4702 a-4702 n encapsulated in the first protocol 4704 may havehttp protocol packets related to displaying the web page and receivingany user interaction to communicate to the host service 4516 a-4516 n.Since the transport connection (4706, 4802) is not maintained by thesecondary protocols 4702 a-4702 n, the secondary protocols 4702 a-4702 ndo not need to handle any network-level connection interruptions. Assuch, the secondary protocols 4702 a-4702 n may not provide anynetwork-level connection interruption information in their payloads. Inthe above example, the http related secondary protocol packets 4902a-4902 n of the secondary protocol 4702 a-4702 n transmitted to theclient machine 10 would not provide a notification that a networkinterruption occurred, e.g., an error message on a web page. Therefore,the user on the client machine 10 will not be notified of anynetwork-level connection interrupts through the secondary protocol 4702a-4702 n. This effectively hides the network connection interruptionsfrom the user during the use of the applications related to thesecondary protocols 4702 a-4702 n.

Referring to FIG. 49, an example process 4900 used by the first protocolservice 4502 and the client agent 4506 of the client machine 10encapsulates the plurality of secondary protocols 4702 (e.g., HTTP, FTP,Oscar, Telnet, ICA, and/or RDP) within the first protocol 4704 forcommunication via the connection 4504. Optionally, as described below,the example process 4900 used by the first protocol service 4502 and theclient agent 4506 of the client machine 10 also compresses and/orencrypts the communications at the level of the first protocol prior tocommunications via the connection 4504. From the point of view of thefirst protocol service 4502, secondary protocol packets 4902 a-4902 nare received via the connections 4508 a-4508 n at the first protocolservice 4502. For example, two secondary protocol packets 4902 a and4902 b are received by the first protocol service 4502. One, two, or anynumber of secondary protocol packets 4902 a-4902 n can be received. Inone embodiment, the secondary protocol packets 4902 a-4902 n aretransmitted by the host services 4516 to the first protocol service 4502over the connection 4508. The secondary protocol packets 4902 a-4902 ninclude a header 4904 and a data packet 4906, also referred to as a datapayload.

Following receipt of the secondary protocol packets 4902 a-4902 n, thefirst protocol service 4502 encapsulates one or more of the secondaryprotocol packets 4902 within a first protocol packet 4908. In oneembodiment, the first protocol service 4502 generates a first protocolpacket header 4910 and encapsulates within the data payload 4912 of thefirst protocol packet 4908 one or more secondary protocol packets 4902a-4902 n, such as, for example, two secondary protocol packets 4902 aand 4902 b. In another embodiment, only one secondary protocol packet4902 a is encapsulated in each first protocol packet 4908.

In one embodiment, the first protocol packets 4908 are then transmittedover the connection 4504, for example over the connection 4706 describedwith reference to FIG. 47, to the client agent 4506 of the clientmachine 10. Alternatively, in another embodiment, the first protocolservice 4502 is further configured to encrypt, prior to the transmissionof any first protocol packets 4908, communications at the level of thefirst protocol 4704. In one such embodiment, the first protocol packets4908 are encrypted by using, for example, the SSL protocol describedwith reference to FIG. 48. As a result, a secure packet 4914, includinga header 4916 and an encrypted first protocol packet 4908′ as a datapayload 4918, is generated. The secure packet 4914 can then betransmitted over the connection 4504, for example over the secure TCP/IPconnection 4802 illustrated in FIG. 48, to the client agent 4506 of theclient machine 10.

In another embodiment, the first protocol service 4502 is furtherconfigured to compress, prior to the transmission of any first protocolpackets 4908, communications at the level of the first protocol 4704. Inone embodiment, prior to encrypting the first protocol packet 4908, thefirst protocol service 4502 compresses, using a standard compressiontechnique, the first protocol packet 4908. As such, the efficiency ofthe system 4502 is improved.

Referring again to FIGS. 45-46, in one embodiment, the system 4500provides the remote client machine 10 with a persistent connection to aremote machine 30, such as, for example, the remote machine 30′. Forexample, if the client machine 10 establishes a connection 4504 betweenthe client machine 10 and the first protocol service 4502 and the firstprotocol service 4502 establishes a connection 4508 a between the firstprotocol service 4502 and the remote machine 30′, then either the clientagent 4506, the first protocol service 4502, or both are configured tomaintain a queue of the first protocol data packets most recentlytransmitted via the connection 4504. For example, the queued datapackets can be maintained by the client agent 4506 and/or the firstprotocol service 4502 both before and upon a failure of the connection4504. Moreover, upon a failure of the connection 4504, the firstprotocol service 4502 and, likewise, the remote machine 30 areconfigured to maintain the connection 4508 a.

Following a failure of the connection 4504, the client machine 10establishes a new connection 4504 with the first protocol service 4502,without losing any data. More specifically, because the connection 4508a is maintained upon a failure of the connection 4504, a newlyestablished connection 4504 can be linked to the maintained connection4508 a. Further, because the most recently transmitted first protocoldata packets are queued, they can again be transmitted by the clientmachine 10 to the first protocol service 4502 and/or by the firstprotocol service 4502 to the client machine 10 over the newlyestablished connection 4504. As such, the communication session betweenthe remote machine 30′ and the client machine 10, through the firstprotocol service 4502, is persistent and proceeds without any loss ofdata.

In one embodiment, the client agent 4506 of the client machine 10 and/orthe first protocol service 4502 number the data packets that theytransmit over the connection 4504. For example, each of the client agent4506 and the first protocol service 4502 separately numbers its owntransmitted data packets, without regard to how the other is numberingits data packets. Moreover, the numbering of the data packets can beabsolute, without any re-numbering of the data packets, i.e., the firstdata packet transmitted by the client agent 4506 and/or the firstprotocol service 4502 can be numbered as No. 1, with each data packettransmitted over the connection 4504 by the client agent 4506 and/or thefirst protocol service 4502, respectively, consecutively numberedthereafter.

In one such embodiment, following a disrupted and re-establishedconnection 4504, the client agent 4506 and/or the first protocol service4502 informs the other of the next data packet that it requires. Forexample, where the client agent 4506 had received data packets Nos. 1-10prior to the disruption of connection 4504, the client agent 4506, uponre-establishment of the connection 4504, informs the first protocolservice 4502 that it now requires data packet No. 11. Similarly, thefirst protocol service 4502 can also operate as such. Alternatively, inanother such embodiment, the client agent 4506 and/or the first protocolservice 4502 informs the other of the last data packet received. Forexample, where the client agent 4506 had received data packets Nos. 1-10prior to the disruption of connection 4504, the client agent 4506, uponre-establishment of the connection 4504, informs the first protocolservice 4502 that it last received data packet No. 10. Again, the firstprotocol service 4502 can also operate as such. In yet anotherembodiment, the client agent 4506 and/or the first protocol service 4502informs the other, upon re-establishment of the connection 4504, of boththe last data packet received and the next data packet it requires.

In such embodiments, upon re-establishment of the connection 4504, theclient agent 4506 and/or the first protocol service 4502 can retransmitthe buffered data packets not received by the other, allowing thecommunication session between a host service 4516 and the client machine10, through the first protocol service 4502, to proceed without any lossof data. Moreover, upon re-establishment of the connection 4504, theclient agent 4506 and/or the first protocol service 4502 can flush fromeach of their respective buffers the buffered data packets now known tobe received by the other.

By providing the client machine 10 with a reliable and persistentconnection to a remote machine 30, the process of opening a new usersession with the remote machine 30 is avoided by maintaining the usersession through network connection interruptions. For each user sessionwith a remote machine 30, the client machine 10 and the remote machine30 may maintain session specific context and caches, and otherapplication specific mechanisms related to that instance of the usersession. For each new user session established, these session-specificcontext and caches need to be re-populated or re-established to reflectthe new user session. For example, a user on the client machine 10 mayhave an http session with a remote machine 30. The remote machine 30 maykeep context-specific information of this instance of the http sessionwith the client machine 10. The context may be stored in the memory ofthe server, in files of the server, a database or other componentrelated to providing the functionality of the remote machine 30. Also,the client machine 10 may have local context specific to the instance ofthe http session, such as a mechanism for keeping track of anoutstanding request to the remote machine 30. This context may be storedin memory of the client machine 10, in files on the client machine 10,or other software component interfaced with the client machine 10. Ifthe connection between the client machine 10 and the remote machine 30is not persistent, then a new user session needs to be established withnew session specific context on the remote machine 30 and the clientmachine 10. The session is maintained so that a new session, andtherefore new specific session context, does not need to bere-established.

In some embodiments, the user session is maintained through networklevel connection interruptions and without notification to the user ofthe client that the session was interrupted. In operation of theseembodiments, the first protocol service 4502 establishes and maintains afirst connection with a client machine 10 and a second connection with ahost service 4516 a-4516 n. Via the first connection and the secondconnection, a session between the client machine 10 and the remotemachine 30 is established. The first protocol service 4502 can store andmaintain any session-related information such as authenticationcredentials, and client machine 10 and remote machine 30 context for theestablished session. A user on the client machine 10 will exercise thefunctionality provided by the remote machine 30 through the establishedsession. As such, related secondary protocol packets 4902 a-4902 n willcontain data related to the transaction of such functionality. Thesesecondary protocol packets 4902 a-4902 n as part of the secondaryprotocol 4702 a-4702 n are encapsulated and communicated in a firstprotocol 4704. Upon detection of a disruption in either the firstconnection or the second connection, the first protocol service 4502 canre-establish the disrupted connection while maintaining the otherconnection that may have not been disrupted. The network connectiondisruption may cause an interruption to the session between the clientmachine 10 and the remote machine 30. However, since the transportmechanism is not maintained by the secondary protocols 4702 a-4702 n,the session can be re-established after the network connection isre-established without the user on the client machine 10 havingnotification that the session was interrupted. The secondary protocol4702 a-4702 n does not need to contain any interruption relatedinformation to transmit to the client machine 10. Thus, the interruptionof the session caused by the network connection disruption iseffectively hidden from the user because of the encapsulation of thefirst protocol 4704.

The first protocol service 4502 maintaining session related informationcan re-establish the session between the client machine 10 and theremote machines 30. For example, if the first connection between theclient machine 10 and the first protocol service 4516 is disrupted, thefirst protocol service 4502 can keep the client machine 10's sessionactive or open between the first protocol service 4502 and the remotemachine 30. After the first connection is re-established, the firstprotocol service 4502 can link the session of the client machine 10 tothe maintained session between the first protocol service 4502 and thehost service 4516. The first protocol service 4502 can send to theclient machine 10 any data that was queued prior to the disruption inthe first connection. As such, the client machine 10 will be using thesame session prior to the disruption, and the remote machine 30 andclient machine 10 can continue to use any session specific context thatmay have in memory or stored elsewhere. Furthermore, because of theintermediary of the first protocol service 4502, the remote machine 30may not be aware of the network disruption between the first protocolservice 4502 and the client machine 10.

In another example, if the second connection between the first protocolservice 4502 and the remote machine 30 is disrupted, the first protocolservice can maintain the first connection with the client machine 10while re-establishing the second connection with the remote machine 30.After re-establishing the second connection, the first protocol service4502 can re-establish the client's session, on behalf of the client,with the remote machine 30. Since the first protocol service 4502 wasmaintaining any session relation information, the first protocol servicemay re-establish the same session or a similar session so that theclient machine 10 is not aware of the disruption in the second networkconnection and the resulting disruption to the session between the firstprotocol service 4502 and the remote machine 30. During re-establishingthe second network connection and the session, the first protocolservice 4502 can queue any session transactions sent by the clientmachine 10 during the disruption. Then, after re-establishing thesession with the remote machine 30, the first protocol service 4502 cantransmit the queued transactions to the remote machine 30 and thesession can continue normally. In this manner, the client machine 10continues to operate as if there was not an interruption to the session.

Additionally, by providing a reliable and persistent connection, someembodiments also avoid interruptions to transactions, commands oroperations as part of the functionality exercised between the clientmachine 10 and a remote machine 30, or a remote machine 30. For example,a file copy operation using Windows Explorer has not been designed tocontinue working after there is a disruption in a network connection. Auser on the client machine 10 may use the file copy feature of WindowsExplorer to copy a file from the client machine 10 to a remote machine30. Because of the size of the file or files, this operation may take arelatively extended period of time to complete. If during the middle ofthe operation of the copy of the file to the remote machine 30, there isan interruption in the network connection between the client machine 10and the remote machine 30, the file copy will fail. Once the networkconnection is re-established, the user will need to start another filecopy operation from Windows Explorer to copy the file from the clientmachine 10 to the remote machine 30. Under some embodiments of themethods described above, the user would not need to start another filecopy operation. The network connection would be re-established as partof the first protocol 4704 connection. The file copy operations would beencapsulated in the payload of the secondary protocols 4702 a-4702 n. Assuch, the file copy of Windows Explorer would not get notified of theinterruption in the network connection and therefore, would not fail.The first protocol service 4502 would re-establish any connections andtransmits any queued data so that operation can continue withoutfailure. The first protocol service 4502 would maintain a queue of thedata related to the file copy operations that has not been transferredto the remote machine 30 because of the interruption in the networkconnection. Once the network connection is re-established, the firstprotocol service 4502 can transmit the queued data and then continue onwith transferring the data related to the file copy operation in duecourse.

Although these embodiments are described in terms of a file copyoperation example, one ordinarily skilled in the art will recognize thatany operation, transaction, command, function call, etc. transactedbetween the client machine 10 and the remote machine 30, or remotemachines 30, can be maintained and continued without failure from thenetwork connection disruption, and, furthermore, without the clientmachine 10 recognizing there was a disruption or having notice of thedisruption.

Furthermore, by providing a reliable and persistent connection, a clientmachine 10 is able to traverse through different network topologieswithout re-starting a session or an application on the client machine10. For example, the client machine 10 may be a computer notebook with awireless network connection. As the client machine 10 moves from a firstwireless network to a second wireless network, the client's networkconnection 4504 may be temporarily disrupted from the first wirelessnetwork as a network connection is established with the second wirelessnetwork. The second wireless network may assign a new networkidentifier, such as a host name or internet protocol address, to theclient machine 10. This new network identifier may be different than thenetwork identifier assigned to the client machine 10 by the firstwireless network. In another example, the client machine 10 may bephysically connected through an Ethernet cable to a port on the network.The physical connection may be unplugged and the client machine 10 movedto another location to plug into a different port on the network. Thiswould cause a disruption into the network connection 102 and possible achange in the assigned network identifier. By the method and systemsdescribed herein, the network connection is maintained for the clientand automatically re-established the network connection of the clientmachine 10, including handling changes in the network topology andnetwork identifier. The client machine 10, and any applications orsessions on the client machine 10, can continue to operate as if therewas not a network connection disruption or a change in the networkidentifier. Furthermore, the user on the client machine 10 may notrecognize there were any interruptions or changes, and the clientmachine 10 may not receive any notice of such interruptions.

Even with a reliable and persistent communication session as describedabove, network connections are still disrupted. When re-establishing theclient's connection to the host service, the client machine 10 alsoneeds to be re-authenticated to the remote machine 30. In oneembodiment, systems and methods authenticate a client machine 10 to ahost service 4516 and re-authenticate the client machine 10 to theremote machine 30 without re-entering authentication credentials.

In another embodiment, securely establishing a communication sessionbetween the client machine 10 and the host service 4516 is enabled viamultiple connections or “hops” that traverse multiple networkcomponents, such as a proxy, security gateway, firewall or router. Theestablishment of the multiple hop secure communication session mayfurther be initiated via a secure client-web server communicationchannel, for example, between the web browser 6302 and a first remotemachine 30 using SSL. The ticket authority 6102 can provide tickets foreach of the hops such as the client-first protocol service connection4504 and the first protocol service to host service connections 4508a-4508 n. In this manner, the client machine 10 is authenticated throughall the connections between the client machine 10 and the host service4516 a-45116 n.

In some embodiments, a first remote machine 30, functioning as a webserver, receives a request from the client machine 10 for an applicationand the first remote machine 30 validates the request with the ticketauthority 6102. The ticket authority 6102 then generates an N partticket (e.g., T₁ to T_(N)). In one embodiment, the ticket authority 6102then transmits a portion T_(i) of the N part ticket (e.g., the firstpart of the ticket, or first ticket T₁) to the first remote machine 30.The first remote machine 30 then transmits the ticket T₁ to the clientmachine 10. In one embodiment, the ticket authority 6102 also transmitsthe address of the next “hop” (e.g., the first protocol service 4502 tothe first remote machine 30, which then transmits the address to theclient machine 10. This address is the address of the next hop (e.g.,first protocol service 4502) that this hop (e.g., client machine 10)needs to communicate with for the client machine 10 to eventually beauthenticated to the remote machine 30.

The client machine 10 uses the address to then contact the next “hop”(e.g., first protocol service 4502) and initiates a communicationsession with the first protocol service 4502 a by transmitting a proxyconnection request over the client-first protocol service communicationchannel 4504. The first protocol service 4502 a then extracts the firstticket T₁ from the proxy connection request and forwards this ticket tothe ticket authority 6102 for validation. The ticket authority 6102 thenvalidates the first ticket T₁.

Upon proper verification of the first ticket T₁, the ticket authority6102 transmits the next ticket T_(i) from the N part ticket (e.g., T₂)to the next first protocol service 4502 (e.g., first protocol service4502 a). In some embodiments, the ticket authority 6102 also transmitsthe address of the next hop (e.g., the second first protocol service4502 b) to this hop (e.g., the first protocol service 4502 a). The firstprotocol service 4502 a transmits this ticket to the next hop (e.g., thesecond first protocol service 4502 b). In one embodiment, the secondfirst protocol service 4502 b verifies T₂ by transmitting the ticket tothe ticket authority 6102. The ticket authority 6102 validates thesecond ticket T₂ and the process continues. Once the last part of the Npart ticket has been validated the application is launched on the clientmachine 10.

In one embodiment, each first protocol service 4502 (i.e., each hop)validates T_(i) (e.g., T₂) with a ticket authority 6102 associated withthe first protocol service 4502 (i.e., hop). In this embodiment, aftereach first protocol service 4502 validates the ticket T_(i) (e.g., T₂)with a ticket authority 6102, the ticket authority 6102 at which thevalidation took place transmits the next ticket T_(i+1) (e.g., T₃) andthe address of the next first protocol service 4502 (i.e., the next“hop” destination) to the first protocol service 4502 that had validatedthe ticket T_(i). Thus, each first protocol service 4502 is associatedwith a ticket authority 6102 that has been configured with the currentand next hop tickets (i.e., validating T_(i) and transmitting T_(i+1)for the next hop). Consequently, the next first protocol service 4502acts as the client for that hop. This process is repeated until reachingthe remote machine 30. Thus, each hop has been validated individuallywithout revealing all of the ticket to any one hop.

In other embodiments, the ticket authority 6102 may issue more than oneticket rather than issuing one ticket having many parts. For example,the ticket authority 6102 generates a first hop ticket and a second hopticket, where the first hop ticket has no association with the secondhop ticket. The ticket authority 6102 subsequently transmits the firsthop ticket to the first remote machine 30 and the first remote machine30 transmits the first hop ticket to the client machine 10. The clientmachine 10 transmits this first hop ticket to the first protocol service4502 (e.g., first protocol service 4502 a) for validation by the ticketauthority 6102. Upon validation, the ticket authority 6102 transmits thesecond hop ticket to the next first protocol service 4502 (e.g., secondfirst protocol service 4502 b) while the first hop ticket is independentfrom the second hop ticket.

In a further embodiment, one or more of the ticket authorities 6102provides proxies, either as part of the first protocol service 4502 orseparated from the first protocol service 4502, with any necessaryinformation needed to connect to the next hop, such as, but withoutlimitation, encryption keys, SSL method configuration information, andauthentication information to connect to a SOCKS server (e.g., SOCKS5server, developed by NEC Corporation of Tokyo, Japan).

In yet another embodiment, a ticket authority 6102 only generates asingle ticket. The ticket authority 6102 transmits the single ticket tothe first remote machine 30. The first remote machine 30 forwards thesingle ticket to the client machine 10. The first protocol service 4502subsequently receives the ticket from the client machine 10 and“consumes” the single ticket upon validation. As a result, a singleticket can provide the ability to use arbitrary communication protocolsover the client-proxy communication channel 4504 and the client-webserver communication channel. Additionally, because the remote machine30 does not receive or verify the single ticket, the ticket istransparent to the remote machine 30 and, consequently, the remotemachine 30 is not “aware” of the use of the ticket.

By exploiting the security of the secure communications between theclient machine 10 and the first remote machine 30 over the secureclient-web server communication channel, the system establishes a securecommunication link over the non-secure client-proxy communicationchannel 4504 to remotely display desktop applications securely on theclient machine 10.

In yet another embodiment, the ticket authority 6102 transmits adisabled version of the first protocol service ticket with the clientticket to the first remote machine 30 for transmission to the clientmachine 10. The client machine 10 subsequently transmits the firstprotocol service ticket along with the client ticket to the firstprotocol service 4502 as part of the proxy connection request. The firstprotocol service 4502 then forwards both tickets to the ticket authority6102. Upon receiving a disabled first protocol service ticket, theticket authority 6102 enables the first protocol service ticket aftervalidating the client ticket. The ticket authority 6102 then transmitsthe enabled first protocol service ticket to the first protocol service4502 for authentication to the host node 118.

Alternatively, in another embodiment the first remote machine 30receives a disabled first protocol service ticket and an enabled clientticket from the ticket authority 6102 and only transmits the clientticket to the client machine 10. The client machine 10 transmits theclient ticket to the first protocol service 4502 as part of the proxyconnection request. The first protocol service 4502 then forwards theclient ticket to the ticket authority 6102. The ticket authority 6102validates the client ticket and, upon validation, enables the firstprotocol service ticket previously transmitted to the first remotemachine 30. In yet another embodiment, the ticket authority 6102transmits an enabled first protocol service ticket to the first remotemachine 30 upon validation of the client ticket for authentication tothe remote machine 30.

Thus, at any given time, the ticket authority 6102 provides only oneticket that is enabled to the client machine 10 or first protocolservice 4502 that the ticket authority 6102 can validate. The ticketauthority 6102 may provide another ticket that can't be validated (i.e.,a disabled ticket) until the enabled ticket is validated. Alternatively,the ticket authority 6102 may not transmit the first protocol serviceticket to the first protocol service 4502 until the ticket authority6102 validates the enabled ticket. As discussed in further detail below,this enforces network routing of communications using embodiments ofthis system because the client machine 10 cannot traverse the firstremote machine 30 or the first protocol service 4502 without having theticket authority 6102 validate the enabled ticket and transmit theticket needed to communicate with the remote machine 30.

In another embodiment, instead of transmitting the first protocolservice ticket to the first protocol service 4502, the ticket authority6102 transmits the first protocol service ticket to the first remotemachine 30 directly over a web server-authority communication channel.The first remote machine 30 then automatically transmits the firstprotocol service ticket to the remote machine 30. In other words, thefirst remote machine 30 “pushes” the first protocol service ticket tothe remote machine 30. The ticket authority 6102 can also push the firstprotocol service ticket to the remote machine 30 without transmission ofthe first protocol service ticket to the first protocol service 4502 orthe first remote machine 30.

In yet another embodiment, the remote machine 30 retrieves the firstprotocol service ticket from the ticket authority 6102 over theticket-content server communication channel 157. In other words, theremote machine 30 “pulls” the first protocol service ticket from theticket authority 6102.

Moreover, the system enforces the routing of the client machine 10through the first protocol service 4502. As stated above, the clientmachine 10 has to possess the first protocol service ticket to establisha communication session with the remote machine 30. More specifically,to establish a connection with the remote machine 30, the first remotemachine 30 first has to validate the request of the client machine 10with the ticket authority 6102. Once validated, the client machine 10obtains the first ticket and transmits this first ticket to the ticketauthority 6102 for validation. However, upon validation, the ticketauthority 6102 transmits the first protocol service ticket back to thefirst protocol service 4502 rather than the client machine 10. Thecommunication session between the client machine 10 and the host service4516 is established when the host service 4516 receives the firstprotocol service ticket. Thus, the client machine 10 has to communicatewith the first protocol service 4502 in order to have the first protocolservice ticket transmitted to the host service 4516, thereby enforcingthe routing of the client machine 10 through the first protocol service4502. Thus, the invention can ensure the proper traversal of a securitydevice (e.g., the first protocol service 4502) before granting access tothe remote machine 30.

For example, a remote machine 30 executes several applications, such asMICROSOFT WORD and MICROSOFT EXCEL, both developed by MicrosoftCorporation of Redmond, Wash. In one embodiment, the client machine 10uses NFUSE, developed by Citrix Systems, Inc. of Fort Lauderdale, Fla.,to obtain information from the machine farm 38 in which applications canbe accessed by the client machine 10. If a client user wants to accessand use MICROSOFT WORD, the client machine 10 requests the applicationfrom the first remote machine 30. However, only users who pay anapplication fee for MICROSOFT WORD can become authorized to access theapplication.

To ensure the payment of the application fee, the system includes thefirst protocol service 4502 and the ticket authority 6102 to enforce therouting of the client machine 10 through the first protocol service4502. The routing of the client machine 10 through the first protocolservice 4502 is valuable to the application provider if the firstprotocol service 4502 is used to collect the application fee andauthorize the user for access to the application.

The ticket authority 6102 subsequently generates a ticket associatedwith the request for the application. An enabled first ticket is thentransmitted to the client machine 10. Because the client machine 10 doesnot have the address of the host node 118, the client machine 10 cannotaccess the application. Further, the client machine 10 has not beenauthorized by the first protocol service 4502 yet (i.e., has not yetpaid). Thus, the client machine 10 has to communicate with the firstprotocol service 4502 to become authorized. The first protocol service4502 can then transmit the enabled first ticket to the ticket authority6102 upon payment of the application fee.

The ticket authority then validates the client ticket and subsequentlytransmits (or enables) a first protocol service ticket to the proxy. Thefirst protocol service 4502 then transmits the first protocol serviceticket to the remote machine 30 (e.g., assuming the client user has paidthe application fee), which enables the remote machine 30 to transmitthe application to the client machine 10.

FIG. 50 depicts one embodiment of a system 5000 that is capable ofreconnecting the client machine 10 to a host service 4516 using anautomatic client reconnect service referred to as auto client reconnectservice or ACR Service 5002. In brief overview, a client machine 10communicates with a remote machine 30, also referred to as a server,over a communication channel 5004. The communication channel 5004 mayinclude a network 150. For example, the communication channel 5004 canbe over a local-area network (LAN), such as a company Intranet, or awide area network (WAN) such as the Internet or the World Wide Web. Theremote machine 30 provides auto client reconnect services through an ACRService 5002. The client machine 10 accesses the remote machine 30through the communication channel 5004. The ACR Service 5002 of theremote machine 30 provides authentication services to authenticate theclient machine 10 to the remote machine 30. When there is a disruptionin a network connection, the ACR Service 5002 further providesre-authentication services to re-authenticate the client machine 10 tothe remote machine 30. Although described with a single client machine10 and one communication channel 5004, any number of clients (e.g. 10,10′) and number of communication channels (e.g. 5004, 5004′) can be partof the system 4500.

The ACR Service 5002 running on the remote machine 30 includes a keygenerator 5006, a session identifier (SID) generator 5008, an encryptor5010, a key destroyer 5012, and a decryptor 5014. The key generator 5006generates a key when the remote machine 30 or the ACR Service 5002receives authentication credentials from the client machine 10. In oneembodiment, the key generator 5006 derives the key from a characteristicof the remote machine 30. Particular examples include the key generator5006 deriving the key from the temperature of the processor 5016, thetime that remote machine 30 received the authentication credentials, andthe number of keys stored in memory 5018. In a further embodiment, thekey and the authentication credentials are the same size (e.g. eightbits). In one embodiment, the key generator is a software module. Inanother embodiment, the key generator 5006 is a random number generator.

The SID generator 5008 generates the unique SID to enable the remotemachine 30 to identify a particular communication session. In oneembodiment, the SID generator 5008 is a software module. In anotherembodiment, the SID generator 5008 is a random number generator. Inanother embodiment, the SID generator transmits the SID to the hostservice 4516. In one embodiment, the SID generator 5008 obtains the SIDfrom a host service 4516 running on the server. In yet anotherembodiment, the SID generator generates the SID by receiving a sessionidentifier from the host servicel 16 establishing a user session.

The encryptor 5010 encrypts the key with the authentication credentialsto create encrypted authentication credentials. In one embodiment, theencryptor 5010 encrypts the key with the authentication credentials byperforming an exclusive OR operation (i.e. XOR) on the key and theauthentication credentials. In another embodiment, the encryptor 5010adds the authentication credentials to the key to encrypt theauthentication credentials; that is, the encryptor 5010 performs a“Caesar Cipher” on the authentication credentials using the key as theshift value. In another embodiment, the encryptor 5010 performs a hashfunction, such as MD4, MD5, or SHA-1, on the authentication credentials.It should be clear that the encryptor 5010 can perform any type ofmanipulation on the authentication credentials as long as the ACRService 5002 can decrypt the encrypted authentication credentials withthe key.

In one embodiment, the encryptor 5010 is a software module that executesmathematical algorithms on the key and the authentication credentials tocreate the encrypted authentication credentials. In another embodiment,the encryptor 5010 is a logic gate of the remote machine 30, such as anexclusive OR (XOR) gate.

In one embodiment, the encryptor 5010 stores the encryptedauthentication credentials with the SID in a table 5020 in memory 5018.In another embodiment, the encryptor 5010 stores the encryptedauthentication credentials in the table 5020 and the SID generator 5008stores the SID in the table 5020. In one embodiment, the table 5020 isan area in memory 5018 allocated by the processor 5016 for us by theencryptor 5010. In another embodiment, the encryptor 5010 stores theencrypted authentication credentials with the SID in a database (notshown in FIG. 50) separate from memory 5018.

In one embodiment, the ACR Service 5002 uses the SID as a vector to thelocation of the encrypted authentication credentials in the table 5020.In another embodiment, the ACR Service 5002 uses the SID as a databasekey to locate and retrieve the encrypted authentication credentials in adatabase (not shown in FIG. 50). Each encrypted authenticationcredential created by the encryptor 5010 is associated with only oneunique SID. Thus, the ACR Service 5002 can locate and retrieve theencrypted authentication credentials by using a particular SID.

The key destroyer 5012 deletes the key once the ACR Service 5002determines that the key is no longer needed. In one embodiment, the keydestroyer 5012 is a delete function of a software program such as theoperating system of the remote machine 30.

The decryptor 5014 decrypts the encrypted authentication credentialsonce the ACR Service 5002 receives the key and the SID from the clientmachine 10. In one embodiment, the decryptor 5014 is a software modulethat performs the inverse function or algorithm that the encryptor 5010performed to create the encrypted credentials. In another embodiment,the decryptor 5014 is a hardware component (e.g. a logic gate) toperform the inverse operation of the encryptor 5010.

In one embodiment, one or more of the key generator 5006, the SIDgenerator 5008, the encryptor 5010, the key destroyer 5012 and thedecryptor 5014 are joined into one software module representing the ACRService 5002. In another embodiment, these components can be hardwarecomponents such as logic gates. In a further embodiment, thesecomponents are included in a single integrated circuit. In yet anotherembodiment, some of the components, for example the key generator 5006and the SID generator 5008, can be hardware components, and othercomponents, for example the encryptor 5010, the key destroyer 5012 andthe decryptor 5014, can be software components.

In another embodiment, methods for reconnecting a client machine 10 to aremote machine 30 when there is a disruption in the client's connectionto the network are provided. The methods include re-establishing theclient's connection to the remote machine 30 and using the ACR Service5002 to re-authenticate the client to the host service.

Referring to FIG. 51, the client machine 10 establishes a firstcommunication session with the remote machine 30 over the communicationchannel 5004. The client machine 10 obtains (step 54100) authenticationcredentials from a user of the client machine 10. In a system 4500 notusing an Open System Interconnection (OSI) protocol as the transmissionprotocol for communications between the client machine 10 and the remotemachine 30, the authentication credentials may be a login password thatis needed to establish the first communication session. In thisembodiment, the obtaining of the authentication credentials from theuser precedes the establishment of the communication session. In anotherembodiment, the authentication credential is personal information of theuser that the client machine 10 obtains after the first communicationsession has been established. Examples of authentication credentialsinclude a login password, a social security number, a telephone number,an address, biometric information, a time-varying pass code and adigital certification. The client machine 10 then transmits (step 5405)the authentication credentials to the remote machine 30 over thecommunication channel 5004 so that the remote machine 30 canauthenticate the client machine 10 or the user of the client machine 10.

After the remote machine 30 receives the authentication credentials, theACR Service 5002 provides its auto client reconnect services. The keygenerator 5006 creates (step 5410) a first encryption key for use withthe authentication credentials. In one embodiment, the encryption key isa random number. In another embodiment, the encryption key is anystandard cryptographic key. The encryptor 5010 then encrypts (step 5415)the authentication credentials with the first key to generate encryptedauthentication credentials. This prevents an attacker who gains accessto the remote machine 30 from accessing the authentication credentialswithout the key. The SID generator 5008 then creates (step 5120) a firstSID to identify the first communication session between a client machine10 and the remote machine 30. In one embodiment, the first communicationsession is with a host service 4516 hosted by the remote machine 30. Theencryptor 5010 then stores (step 5425) the encrypted authenticationcredentials with the first SID in the table 5020 described above.

In one embodiment, the encryptor 5010 stores the encryptedauthentication credentials with the first SID in a certain location formore efficient retrieval at a later time. For instance, the encryptor5010 stores all encrypted authentication credentials and SIDs that havebeen created within a predetermined amount of time in RAM. The ACRservice 5002 transfers all encrypted authentication credentials and SIDScreated before a predetermined time to a second, external memory (notshown). In another embodiment, the encryptor 5010 stores the encryptedauthentication credentials with the SID in a database (not shown).

The SID and the encrypted authentication credentials stored in thememory 5018 can be arranged in any particular order and/or format. Forexample, the SID and encrypted authentication credentials can be storedin chronological order with respect to the creation time of theencrypted authentication credentials.

The remote machine 30 then transmits (step 5430) the first key andassociated first SID to the client machine 10 over the network 150. Theclient machine 10 stores (step 5435) the first key and the first SID inmemory (not shown). Then the key destroyer 5012 of the ACR Service 5002deletes (step 5440) the key stored in memory 5018.

In another embodiment, the ACR Service 5002 does not delete the firstkey from memory 5018 until the ACR Service 5002 has notification thatthe client machine 10 has received the key. For example, the clientmachine 10 transmits an acknowledgment message to the remote machine 30after the client machine 10 successfully received the key. Once the ACRService 5002 receives notification, the key destroyer 5012 then deletes(step 5440) the key from the memory 5018. This prevents the ACR Service5002 from deleting the key before the client machine 10 successfullyreceived the key. By not deleting the key until the acknowledgmentmessage, the ACR Service 5002 can retransmit the key and the SID to theclient machine 10 upon a failure in the transmission.

By deleting the key in step 5440, the ACR Service 5002 does not have themechanism needed to decrypt the encrypted authentication credentialsstored in the table 5020. Thus, if an attacker accesses the memory 5018of the remote machine 30, the attacker can retrieve the encryptedauthentication credentials but cannot decrypt the encryptedauthentication credentials. Therefore, the attacker cannot read theauthentication credentials. In short, the encrypted authenticationcredentials stored on the remote machine 30 do not provide anyinformation that the attacker can interpret or understand. As such, theremote machine 30 does not possess any information to decrypt theencrypted authentication credentials.

In addition, the client machine 10 is the only device that can providethe key to the encrypted authentication credentials. With thepossibility of many client machines 10 as part of the network 150, anattacker may have to attempt to gain access to each client (e.g. 10,10′) individually to find the client machine 10 that possesses thecorrect key. This can be time consuming and tedious and, as a result,may deter an attacker from an attempt to decrypt the encryptedauthentication credentials.

In another embodiment, the remote machine 30 has a timeout feature withrespect to accessing the encrypted authentication credentials. Forinstance, the remote machine 30 starts a timer after the firstcommunication is abnormally terminated. If the timer reached apredetermined value before the client machine 10 re-establishes thesecond communication session and transmits the key to the remote machine30 for decryption, the ACR Service 5002 deletes the encryptedauthentication credentials from the table 5020. If no timer is used, thekey acts as a de facto password for future sessions.

Once the client machine 10 receives the first key and the first SID fromthe remote machine 30 as described above in reference to FIG. 51, thesession can be re-established, as shown in FIG. 52, without requiringthe user to reenter his or her authentication credentials. When adisruption or break occurs in the first communication session (step54100) between the client machine 10 and the remote machine 30, thefirst communication session 5004 needs to be re-established and theclient machine 10 re-authenticated to the remote machine 30. The ACRService 5002 provides a system and method for re-establishing andre-authenticating the client machine 10 to the remote machine 30.

When the client machine 10 and the remote machine 30 re-establish asecond communication session, the client machine 10 transmits the firstkey and the first SID (step 5405) to the remote machine 30. The ACRService 5002 uses the SID (step 5210) to locate and retrieve theencrypted authentication credentials in the server's memory 5018 anduses the key (step 5215) to decrypt the retrieved authenticationcredentials. The remote machine 30 then re-authenticates the clientmachine 10 to the remote machine 30 (step 5220) by validating theauthentication credentials from the client machine 10. In oneembodiment, the authentication and re-authentication is facilitatedthrough the security services provided by the operating system of thecomputing device of the remote machine 30. For example, theauthentication credentials are a login and password to the remotemachine 30. In another embodiment, the authentication andre-authentication is facilitated through application level securityservices of an application or software program on the remote machine 30.For example, the authentication credentials are an application login andpassword to a specific host service 4516.

To illustrate, upon an abnormal termination of a first communicationsession (step 54100) in which the user's login password was theauthentication credential, the client machine 10 attempts to establish asecond communication session with the remote machine 30. As part of therequest to the remote machine 30 to establish a second communicationsession with the remote machine 30, the client machine 10 transmits thekey and the SID (step 5405) of the first terminated communicationsession to the remote machine 30. Instead of prompting the user to enterthe user's login password again, the remote machine 30, through the ACRService 5002, uses the SID (step 5210) to locate and retrieve theencrypted authentication credentials associated with the user, uses thekey (step 5215) to decrypt the retrieved authentication credentials, andreauthenticates the client using the decrypted authenticationinformation (step 5220).

In one embodiment, during the second communication session, the ACRService 5002 creates (step 5225) a second key for the authenticationcredentials and then encrypts (step 5230) the authentication credentialsusing the second key. A second SID is created (step 5235) to identifythe second communication session and associate the session with theclient machine 10. The second encrypted authentication credentials arestored (step 5425) with the second SID in the table 5020.

In this embodiment, the server then transmits (step 5240) the second keyand the second SID to the client machine 10. The client machine 10 thenstores (step 5245) the second key and the second SID in memory (notshown) for future retrieval. The ACR Service 5002 then deletes (Step54150) the second key from the memory 5018. Thus, the ACR Service 5002can only decrypt the second encrypted authentication upon obtaining thesecond key and the second SID from the client machine 10. The ACRService 5002 has created a new key and a new SID for the secondcommunication session that is used with the same authenticationcredentials that the user had transmitted during the first communicationsession. Therefore, a user's authentication credentials do not have tobe retransmitted upon a second communication channel after an abnormaltermination of the first communication session.

Although the invention is discussed in terms of authenticationcredentials, any confidential information which can be maintained acrosssessions if there is a communication failure can be used. Thus if creditcard information is required by an application and the credit cardinformation is sent to the server, the subsequent disconnect between theclient and the server does not require the credit card information to bereentered if this invention is issued. Further, although a sessionidentifier, or SID, is discussed as providing a pointer to the storedauthentication credentials, any number or value which is suitable as apointer may be used.

FIG. 53 depicts another embodiment of a system 5300 that is capable ofreconnecting a client machine 10 to a remote machine 30 using an ACRService 5002 executing on an intermediary machine 30′. The intermediarymachine 30′ is a computing device different from the remote machine 30and can be any remote machine 30 that is capable of communication andthat has sufficient processor power and memory capacity to perform theoperations described herein. In brief overview, the client machine 10 isin communication with an intermediary machine 30′ over a communicationchannel 5004. The communication channel 5004 may include a network 150.The intermediary machine 30′ provides auto client reconnect services,via an ACR Service 5002, to the client machine 10 for the connection ofthe client machine 10 to the remote machine 30. The intermediary machine30′ is in communications with the remote machine 30 over a communicationchannel 5004′. The communication channel 5004′ may include a network150′. The client machine 10 accesses the services of the remote machine30 through the intermediary machine 30′. The ACR Service 5002 on theintermediary machine 30′ provides auto client reconnect services for theconnection of the client machine 10 to the remote machine 30. Althoughillustrated with a single client machine 10 over a communication channel5004, any number of clients and number of communication channels can bepart of the system 5300.

In a further embodiment (not shown), the system 5300 includes multipleintermediary machines 30′ that are in communication with one or moreclient machines 10 through a network 150 over additional communicationchannels 5004, 5004′. Although illustrated in FIG. 53 with a singleintermediary machine 30′ over a communication channel 5004, any numberof intermediary nodes and number of communication channels can part ofthe system 5300.

In another embodiment, the invention relates to methods to facilitateestablishing and authenticating a client machine's 10 connection to aremote machine 30 using one or more intermediary machines 30′. As shownin FIG. 54, an intermediary machine 30′ establishes a session with theremote machine 30.

The client machine 10 establishes a first communication session with theintermediary machine 30′ over the communication channel 5004. The clientmachine 10 obtains (step 5400) authentication credentials from a user ofthe client machine 10. The client machine 10 then transmits (step 5405)the authentication credentials to the intermediary machine 30′ over thecommunication channel 5004 so that the intermediary machine 30′ canauthenticate the user with the remote machine 30.

After the intermediary machine 30′ receives the authenticationcredentials, the ACR Service 5002 provides its auto client reconnectservices. The ACR Service 5002 creates (step 5410) a first encryptionkey for use with the authentication credentials and then encrypts (step5415) the authentication credentials with the first key to generateencrypted authentication credentials. This prevents an attacker whogains access to the remote machine 30 from accessing the authenticationcredentials without the key. Then a session is established with theremote machine 30 (step 5420A) and the client machine 10 isauthenticated to the remote machine 30 using the authenticationcredentials. Thereby, the ACR Service 5002 creates a first SID toidentify the first communication session. The encrypted authenticationcredentials are stored (step 5425) with the first SID in the table 5020described above. The intermediary machine 30′ then transmits (step 5430)the first key and the first SID to the client machine 10 over thenetwork 150. The client machine 10 stores (step 5435) the first key andthe first SID in the client machine's memory (not shown). The ACRService 5002 then deletes (step 5440) the key stored in memory 5018.

Once the client machine 10 receives the first key and the first SID fromthe intermediary machine 30′ as described above in reference to FIG. 54,the communication session can be re-established and re-authenticated, asshown in FIG. 55, without requiring the user to reenter his or herauthentication credentials. For example, there may be a disruption inthe first communication session (step 5505) between the client machine10 and the intermediary machine 30′ from an abnormal termination.

When the client machine 10 and the intermediary machine 30′ re-establisha second communication session, the client machine 10 transmits thefirst key and the first SID (step 5505) to the intermediary machine 30′.The ACR Service 5002 of the intermediary machine 30′ uses the SID (step5510) to locate and retrieve the encrypted authentication credentials inthe server's memory 5018 and uses the key (step 5515) to decrypt theretrieved authentication credentials. The key generator creates (step5520) a second key for the authentication credentials and the keyencryptor 5010 then encrypts (step 5525) the authentication credentialsusing the second key. The SID generator 5008 also creates (step 5530) asecond SID to identify the second communication session and associatesit with the maintained session between the intermediary machine 30′ andthe remote machine 30. The encryptor 5010 stores the second encryptedauthentication credentials with the second SID in the table 5020.

In this embodiment, the remote machine 30 then transmits (step 5535) thesecond key and the second SID to the client machine 10. The clientmachine 10 then stores (step 5540) the second key and the second SID forfuture retrieval. The key destroyer 5012 then deletes (step 5545) thesecond key from the memory 5018. Thus, the ACR Service 5002 can onlydecrypt the second encrypted authentication upon obtaining the secondkey and the second SID from the client machine 10. The ACR Service 5002has created a new key and a new SID for the second communication sessionthat is used with the same authentication credentials that the user hadtransmitted during the first communication session. Therefore, a user'sauthentication credentials do not have to be retransmitted upon a secondcommunication channel after an abnormal termination of the firstcommunication session.

In another embodiment, there may be a disruption or abnormal terminationin the second communication session (step 5600) between the intermediarymachine 30′ and the remote machine 30. As described in FIG. 56, thesecond communication session can be re-established and re-authenticatedwithout requiring the user to reenter his or her authenticationcredentials.

When the intermediary machine 30′ and the remote machine 30 re-establisha second communication session, the intermediary machine 30′ requests(step 5605) the first key and first SID from the client machine 10 tore-establish a session with the remote machine 30 on the client'sbehalf. In response, the client machine 10 transmits the first key andthe first SID (step 5610) to the intermediary machine 30′. The ACRService 5002 of the intermediary machine 30′ uses the SID (step 5615) tolocate and retrieve the encrypted authentication credentials in theserver's memory 5018 and uses the key (step 5620) to decrypt theretrieved authentication credentials. The ACR Service 500 thenre-establishes the client's session with the server (step 5625) usingthe decrypted authentication credentials to re-authenticate the clientmachine 10 to the remote machine 30.

In another embodiment, after re-establishing and re-authenticating theclient over the second communication session, the ACR Service 5002 ofthe intermediary machine 30′ creates a replacement second SID and secondkey as previously described in FIG. 55. In reference to the embodimentof the ACR Service illustrated in FIG. 50, the key generator creates(step 5520) a second key for the authentication credentials and the keyencryptor 5010 then encrypts (step 5525) the authentication credentialsusing the second key. The SID generator 5008 also creates (step 5530) asecond SID to identify the second communication session and associatesit with the re-established session between the intermediary machine 30′and the remote machine 30. The encryptor 5010 stores the secondencrypted authentication credentials with the second SID in the table5020. In this embodiment, the server then transmits (step 5535) thesecond key and the second SID to the client machine 10. The clientmachine 10 then stores (step 5540) the second key and the second SID forfuture retrieval. The key destroyer 5012 then deletes (step 5545) thesecond key from the memory 5018.

In other embodiments, one or more of the first protocol service 4502 andACR Service 5002 can be distributed across any of the host servicenodes. As such, the functionality of re-establishing andre-authenticating, or automatically reconnecting, a client machine 10connect to a host service 4516 can be flexibly distributed in differentsystem and deployment architectures across host services 4516 and/orremote machines 30.

In one embodiment, an ACR Service 5002 can be associated with each ofthe host services 4516 a-4516 n in system 4500 to provide auto clientreconnect services dedicated to each host service 4516, respectively. Asingle first protocol service 4502 can be deployed to handle all of thehost services 4516 a-4516 n. As shown in FIG. 57, each of the multipleACR Services 5002 a-5002 n is associated with each of the host services4516 a-4516 n, respectively. By way of example, a client machine 10establishes a communication session with the host service 4516 a usingthe first protocol service 4502. The ACR Service 5002 a associated withhost service 4516 a provides auto client reconnect services for theconnection of the client machine 10 to the host service 4516 a. If thereis a disruption in a network connection, the first protocol service 4502will re-establish the connection with the client machine 10 and the ACRService 5002 a will re-authenticate the client machine 10 to the hostservice 4516 a. A second client machine 10′ may concurrently, with thefirst client machine 10, establish a communication session with the hostservice 4516 b using the first protocol service 4502. The ACR Service5002 b provides auto client reconnect services for the client'sconnection to the host service 4516 b. If there is a network disruption,the first protocol service 4502 in conjunction with the ACR Service 5002b will reconnect the client machine 10′ to the host service 4516 b.

In another embodiment of these methods, an ACR service can be associatedwith each of the multiple host services 4516 a-4516 n running on each ofthe remote machines 30 of the system 4500. A first protocol service 4502can be deployed on each remote machine 30 to service each of themultiple remote machines 30 running on that host node 118. As shown inFIG. 57, each ACR service 5002 a-5002 n is associated with each hostservice 4516 a-4516 n, respectively. Each remote machine 30 has adedicated first protocol service 4502 servicing each of its hostservices 4516 and each ACR Service 5002. For example, a client machine10 establishes a communication session with host service 4516 a onremote machine 30 by using the first protocol service 4502. The ACRService 5002 a on remote machine 30 provides auto client reconnectservices for the connection of the client machine 10 to the host service4516 a on remote machine 30.

If a network disruption is detected, the first protocol service 4502re-establishes the client's connection to the host service 4516 a onremote machine 30 and the ACR service 5002 a on remote machine 30re-authenticates the client machine 10 to the host service 4516 a onremote machine 30. Concurrently with the first client machine 10, asecond client machine 10′ establishes a communication session with hostservice 4516 b on remote machine 30 using the first protocol service4502 and ACR Service 5002 a. If there is a network disruption, the firstprotocol service 4502 in conjunction with the ACR Service 5002 areconnect the client machine 10′ with host service 4516 b on remotemachine 30. Concurrently with the first client machine 10 and the secondclient machine 10′, a third client machine 10″ establishes acommunication session with host service 4516 n on remote machine 30′using the first protocol service 4502 and ACR Service 5002 n on remotemachine 30′. In a similar manner, the first protocol service 4502 andACR Service 5002 n can reconnect the client machine 10″ to the hostservice 4516 n of remote machine 30′.

In other embodiments, one or more of the ACR Services 5002 can bedistributed with the first protocol services 4502 across any of theintermediary or first protocol services nodes. As such, thefunctionality of reconnecting a client machine 10 to a host service 4516can be flexibly distributed in different system and deploymentarchitectures associated with the first protocol service 4502.

In one embodiment of this aspect of the invention, the ACR Service 5002can be associated with each first protocol service 4502 to provide autoclient reconnect services dedicated to the first protocol service 4502.A single first protocol service 4502 and ACR Service 5002 can bedeployed to handle all of the host services 4516 a-4516 n. As shown inFIG. 59, the ACR Service 5002 resides with the first protocol service4502 on the same computing device to provide auto client reconnectservices to host services 4516 a-4516 n. For example, a client machine10 establishes a communication session with any of the host services4516 a-4516 n by using the first protocol service 4502 and ACR Service5002. The first protocol service 4502 and ACR Service 5002 providereconnecting functionality from a client machine 10 to any of the hostservices 4516 a-4516 n.

In another embodiment of this aspect of the invention, each of the ACRServices 5002 a-5002 n can be associated with each of the multiple offirst protocol services 4516 a-4516 n. For example as shown in FIG. 60,a first protocol service 4502 and an ACR Service 5002 a can be deployedon a remote machine 30 to service each of the multiple host services4516 a-4516 n running on that remote machine 30. As further shown inFIG. 60, each ACR service 5002 a-405 n is associated with each firstprotocol service 4502-112 n to provide dedicated auto client reconnectservices to the multiple host services 4516 a-4516 n of each remotemachine 30-118 n. By way of example, client machine 10 establishes acommunication session with host service 4516 a on remote machine 30 byusing the first protocol service 4502 and ACR Service 5002 a on the sameremote machine 30. If there is a network disruption, the first protocolservice 4502 in conjunction with the ACR Service 5002 a reconnects theclient machine 10 to the host service 4516 a on the remote machine 30.

Although the invention is discussed above in terms of various system anddeployment architectures in FIGS. 57-60, any other system and/ordeployment architecture that combines and/or distributes one or more ofthe first protocol service(s) 4502, ACR Service(s) 5002, and hostservice(s) 4516 across any of the remote machines 30, intermediarymachines 30′ or other computing devices can be used.

Furthermore, instead of using an ACR Service 5002 to provideauthentication and re-authentication services, a ticket authority 6102service can be used. A ticket authority 6102 generates and validatestickets for connection and authentication purposes. A ticket cancomprise a session identifier and key. It can also comprise a randomnumber, an application server certificate, a nonce, a constant or nullvalue or any other type of identification, confidential or securitybased information that may be used for such purposes.

In an embodiment of a network communication system for reconnecting aclient machine 10 to a host service 4516 as shown in FIG. 61, a ticketauthority 6102 can run on a node separate from the intermediary machine30, first protocol service 4502 or any of the host services 4516 a-4516n. FIG. 61 depicts an intermediary machine 30 and ticket authority 6102,which could be a single computing device, as part of the system 4500. Inaddition to the networks 150 and 150′, the system 4500 includes a clientmachine 10, first protocol service 4502, and the host services 4516a-4516 n, all of which are described above. In one embodiment, theintermediary machine 30 is a security gateway, such as, for example, afirewall and/or a router, through which messages between the clientmachine 10 and the first protocol service 4502 must pass due to theconfiguration of the network 150. The ticket authority 6102 can be, forexample, a stand-alone network component that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. The ticketauthority 6102 also can be a specific host service 4516 dedicated toproviding ticket related services on a remote machine 30.

As shown in an embodiment of FIG. 61, the intermediary machine 30 isconfigured to accept a connection 4504 a initiated by the client machine10 and to establish a second connection 4504 b with the first protocolservice 4502. Together, the connection 4504 a and the second connection4504 b constitute the connection 4504, described above, over which theclient machine 10 and the first protocol service 4502 communicate usingthe first protocol.

The intermediary machine 30, as shown, is also configured to communicatewith the ticket authority 6102. In one embodiment, the ticket authority6102 is configured to receive a request for a first reconnection ticketfrom the intermediate node 30′ and to thereafter generate the firstreconnection ticket. The first reconnection ticket can include, forexample, a large random number. The first reconnection ticket allows theclient machine 10 to automatically re-establish a connection with thehost service after an abnormal disruption of service without requiringthe client machine 10 to provide authentication credentials again.

In another embodiment, the ticket authority 6102 is configured toreceive a request for a first re-connection ticket for each of the“hops” between the client machine 10 and host service 4516. For example,the intermediary machine 30 may request re-connection tickets for theconnection between the client machine 10 and the intermediary machine30, between the intermediary machine 30 and the first protocol service4502, and between the first protocol service 4502 and the host service4516. These re-connection tickets may only be valid for each of the“hops”. For example, a first re-connection ticket for the first protocolservice 4502 to host service 4516 connection is valid only forauthenticating the first protocol service 4502 to the host service 4516on behalf of the client machine 10.

After generation of the first reconnection ticket, the ticket authority6102 encrypts the authentication credentials supplied by the clientmachine 10 using the first reconnection ticket so that an attacker whogains access to the intermediary machine 30 or the ticket authority 6102cannot access the authentication credentials without the firstreconnection ticket. The ticket authority 6102 may also generate a SIDto identify the communication session that is established between theclient machine 10 and the intermediary machine 30. The ticket authority6102 then stores the encrypted authentication credentials with the SIDin memory and transmits the SID and the first reconnection ticket to theclient machine 10 over the network 150. Upon the client's receipt of theSID and the first reconnection ticket, the ticket authority 6102destroys (i.e., deletes) the ticket from its memory (not shown).

In another embodiment, the ticket authority 6102 is configured togenerate a handle. The handle can be, for example, a random number thatis associated with (e.g., mapped to) the first reconnection ticket. Inone embodiment, the handle is a smaller random number than the randomnumber forming the first reconnection ticket. For example, the handlemay be a 32-bit random number. In a further embodiment, the handleassociated with a ticket or a re-connection ticket is an address of orpointer to the next “hop” in the multiple-hop connection between theclient machine 10 and the host service 4516. In this case, a ticket orre-connection ticket is validated for a single “hop” with a pointer tothe next “hop”. The next “hop” will need to obtain and validate adifferent ticket or re-connection ticket and so forth until the last“hop” is validated and connected to the host service 4516 on behalf ofthe client machine 10.

The ticket authority 6102 transmits the first reconnection ticket andthe handle to the intermediary machine 30, while keeping a copy of thefirst reconnection ticket and a copy of the handle. The copy of thefirst reconnection ticket can later be used by the ticket authority 6102to validate the first reconnection ticket originally transmitted to theclient machine 10 when it is later presented to the ticket authority6102 during the process of reconnecting the client machine 10. In oneembodiment, the ticket authority 6102 also keeps an address for thefirst protocol service 4502, which, as explained below, is associatedwith the first reconnection ticket and, upon validation of the firstreconnection ticket, is transmitted to the intermediary machine 30.

In one embodiment, the intermediary machine 30 is further configured touse the handle transmitted to it by the ticket authority 6102 to deletethe copy of the first reconnection ticket kept at the ticket authority6102. In another embodiment, as described below, the ticket authority6102 is further configured to delete, during the process of reconnectingthe client machine 10 to a host service 4516, the first reconnectionticket and thereafter generate a replacement first reconnection ticket.Additionally, in another embodiment, the first reconnection ticket isconfigured for automatic deletion after a pre-determined period of time.In the embodiment of re-connection tickets for each of the “hops”between the client and the host service 4516, one, some or all of there-connection tickets may be configured for automatic deletion after apre-determined period of time. In other embodiments, the ticketauthority 6102 or the intermediary machine 30 is configured to deleteeach of the multiple-hop tickets and generate replacement tickets

In another embodiment, the first protocol service 4502 is configured togenerate a second reconnection ticket, which, as in the case of thefirst reconnection ticket, can include, for example, a large randomnumber. In one embodiment, the first protocol service 4502 generatessecond re-connection tickets for each of the “hops” between the clientmachine 10 and the host service 4516. The first protocol service 4502can also be configured to transmit the second reconnection ticket to theclient machine 10, while keeping a copy of the second reconnectionticket and a session number. The copy of the second reconnection ticketcan later be used by the first protocol service 4502 to validate thesecond reconnection ticket originally transmitted to the client machine10 when it is later presented to the first protocol service 4502 duringthe process of reconnecting the client machine 10. In one embodiment,the first protocol service 4502 transmits the second reconnection ticketto the client machine 10 via the intermediary machine 30. In anotherembodiment, the first protocol service 4502 transmits the secondreconnection ticket to the client machine 10 directly. In a furtherembodiment, the first protocol service 4502 may transmit secondre-connection tickets to other first protocol services 4502 orintermediary machines 30 that may comprise the multiple-hop connectionbetween the client machine 10 and the host service 4516.

Moreover, as described in greater detail below, the first protocolservice 4502 can be further configured to delete, during the process ofreconnecting the client machine 10 to a host service 4516, the secondreconnection ticket, and thereafter generate a replacement secondreconnection ticket. Additionally, in another embodiment, the secondreconnection ticket is configured for automatic deletion after apre-determined period of time. In further embodiments, a first protocolservice 4502 of one or more first protocol services 4502 in amultiple-hop connection is configured to delete the second re-connectiontickets for each of the “hops”, and thereafter generate replacementsecond re-connection tickets for one, some or all of the “hops.”

In one embodiment, the intermediary machine 30 serves as an intermediaryfor the first and second reconnection tickets. The intermediary machine30 receives, for example, the first reconnection ticket generated by theticket authority 6102 and the second reconnection ticket generated bythe first protocol service 4502. The intermediary machine 30 can thentransmit the first reconnection ticket and the second reconnectionticket to the client machine 10. Moreover, during the process ofreconnecting the client machine 10 to a host service 4516, theintermediary machine 30 can accept the first reconnection ticket and thesecond reconnection ticket from the client machine 10 and thereaftertransmit the first reconnection ticket to the ticket authority 6102 and,if appropriate, the second reconnection ticket to the first protocolservice 4502.

In another embodiment, the intermediary node 632 serves as anintermediary for the re-connection tickets for the multiple-hops betweenthe client machine 10 and the host service 4516. The intermediarymachine 30 receives, for example, the first re-connection ticket for theclient machine 10 to first protocol service 4502 connection and thefirst re-connection ticket for the first protocol service 4502 to thehost service 4516. In a further embodiment, the intermediary machine 30receives a first re-connection ticket for the connection between theintermediary machine 30 and the first protocol service 4502. Theintermediary machine 30 can then transmit the first re-connection ticketfor the client to the client machine 10 and the first re-connectionticket for the first protocol service 4502 to the first protocol service4502. Moreover, during the process of re-connecting the client machine10 to a host service 4516, the intermediary machine 30 can accept thefirst re-connection ticket from the client machine 10 to validate theticket to re-establish the client's connection to the intermediarymachine 30 or the first protocol service 4502.

If the first communication session between the client machine 10 and thehost service 4516 terminates, for example abnormally, the new sessioncan be re-established without requiring the user to reenter his or herauthentication credentials. When the client machine 10 and the hostservice 4516 re-establish a second communication session, the clientmachine 10 retransmits the first and second reconnection tickets and theSID to the intermediary machine 30. The intermediary machine 30transmits the first and second reconnection tickets and the SID to theticket authority 6102, which uses the SID to locate and retrieve theencrypted authentication credentials for the first connection and usesthe first reconnection ticket to decrypt the retrieved authenticationcredentials. The ticket authority 6102 then authenticates the client byvalidating the decrypted authentication credentials. Afterre-authentication, the second reconnection ticket is forwarded to thefirst protocol service 4502 to re-establish the second connection 4508with the host service 4516.

In another embodiment of a network communications system 6100 as shownin FIG. 62 and 63, the client machine 10 uses the web browser 6302 torequest access to a resource and a first remote machine 30 authenticatesthe user. After receiving the request, the first remote machine 30validates the request with the ticket authority 136. The ticketauthority 6102 then generates a ticket, which includes a first ticket,or client ticket, and a second ticket, or first protocol service ticket.The first and second tickets are “one-time use” tickets having nofurther value after their first use. In still another embodiment, thefirst and second tickets must be used within a predetermined timeperiod.

In one embodiment, the ticket authority 6102 stores the first and secondtickets in memory (e.g., RAM) until the ticket is used. Alternatively,the ticket authority 6102 stores the first and second tickets in astorage device (not shown) until the ticket is used. The storage devicemay include, for example, a database or a persistent memory (e.g., on afloppy disk or hard disk drive). The ticket authority 6102 subsequentlytransmits the client ticket to the first remote machine 30 and the firstremote machine 30 then forwards the client ticket to the client machine10.

The client machine 10 then initiates a communication session with thefirst protocol service 4502 by transmitting a proxy connection requestover the client-first protocol service communication channel 4504. Theproxy connection request includes the client ticket. In one embodiment,the proxy connection request also includes a dummy password that can bereplaced by the first protocol service 4502 when establishing acommunication session with a remote machine 30. In another embodiment,the first remote machine 30 transmits the dummy password to the clientmachine 10 for future generation of a proxy connection request having aformat acceptable to the first protocol service 4502. The first protocolservice 4502 then extricates the client ticket from the proxy connectionrequest and forwards the client ticket to the ticket authority 6102 forvalidation. The ticket authority 6102 then validates the first ticket.In one embodiment, the ticket authority 6102 verifies the first ticketby searching its storage device (e.g., database) for the first expectedticket.

If the ticket authority 6102 does not find the first ticket in thestorage device (such as if the first ticket has been used already), theticket authority 6102 ends the communication session. If the receivedticket matches the client ticket that the ticket authority 6102 expects,the client ticket is validated. The ticket authority 6102 then transmitsthe second or first protocol service ticket to the first protocolservice 4502. Additionally, the ticket authority 6102 deletes the clientticket from the storage device, as the client ticket has now been usedonce. In another embodiment, the ticket authority 6102 also transmitsthe Internet protocol (IP) address of the remote machine 30 to the firstprotocol service 4502. In yet another embodiment, the ticket authority6102 transmits the domain name of the remote machine 30 to the firstprotocol service 4502 for future conversion into the IP address.

The first protocol service 4502 receives the second ticket, or the firstprotocol service ticket, and subsequently opens communications acrossthe proxy-server communication channel 145 by transmitting the secondticket to the remote machine 30. The remote machine 30 receives thefirst protocol service ticket and then transmits the ticket over aticket-server communication channel to the ticket authority 6102 forvalidation. In one embodiment, if the ticket authority 6102 determinesthat the first protocol service ticket received from the remote machine30 has been used previously or does not have the correct value (i.e.,the same value as the value stored in the associated storage device),the ticket authority 6102 transmits an error message to the firstprotocol service 4502 (or the first remote machine 30) to terminate theestablished communication session with the client machine 10. If theticket authority 6102 validates the first protocol service ticket, theremote machine 30 then launches the ICA published application. Theremote machine 30 then transmits application information to the firstprotocol service 4502 for remote displaying of the application on theclient machine 10 using the client agent 4506.

In one embodiment, the client machine 10 launches the client agent 4506when initiating communications with the first protocol service 4502. Inother embodiments, the client machine 10 launches the client agent 4506when the client machine 10 receives the application information from thefirst protocol service 4502.

Thus, the client machine 10 is not aware of the first protocol serviceticket but only the client ticket. Moreover, the client agent 4506cannot access the remote machine 30 without communicating with the firstprotocol service 4502 and presenting the client ticket.

The ticket authority 6102 could also transmit the first protocol serviceticket to the first protocol service 4502 as the user password for theuser of the client machine 10. This allows the first protocol service4502 to use the first protocol service ticket as the login password togain access to the remote machine 30 without exposing the user's loginpassword over the untrusted part of the web (i.e., the non-secureclient-first protocol service communication channel 4504). Thus, in oneembodiment, the communications system 6100 could include a centralizedpassword mapping database managed by the ticket authority 6102 andco-located with the remote machine 30 to map the first protocol serviceticket with a user's password.

Therefore, the password can accompany both tickets (i.e., the firstprotocol service ticket and the client ticket) or the password canaccompany one of the two tickets. As described above, if the passwordaccompanies one of the two tickets, such as the client ticket, then thefirst protocol service ticket is the password. In one embodiment, thepassword can be a system password that does not change in value or maybe a one-time use password, such as those generated by SecurID tokensdeveloped by RSA Security Inc. of Bedford, Mass.

Additionally, the methods described above can be expanded to acommunications system having any number of first protocol services 4502,or “hops” with which the client machine 10 has to communicate beforeestablishing a communication session with the remote machine 30.Although described in relation to a first protocol service 4502, a hopcan comprise any network component, such as a proxy, firewall, router,and relay.

For instance, a four-hop example is a communication system having afirst protocol service 4502 a, a first protocol service 4502 b, and afirst protocol service 4502 n, each protocol service including a proxyand located within the demilitarized zone 6308. The protocol services4502 a-n may communicate with each other over a proxy-proxycommunication channel. The client machine 10 communicates with the firstprotocol service 4502 a which communicates with the second firstprotocol service 4502 b. In turn, the second first protocol service 4502b communicates with the third first protocol service 4502 n and then thethird first protocol service 4502 n communicates with the remote machineover a proxy-server communication channel 4508 to establish thecommunication session with the remote machine. Furthermore, although theembodiment described above includes a ticket having a client ticket anda first protocol service ticket, another embodiment includes the ticketcomprising numerous tickets.

In still another embodiment of a network communications system 6100 asshown in FIG. 62, an ACR Service 5002 can be used instead of the ticketauthority 6102 for reconnecting the client machine 10 to any of the hostservices 4516 a-4516 n. In this embodiment, the ACR Service 5002 canprovide similar services as described above with regards to the ticketauthority 6102. As previously described, the ACR Service 5002 generates,validates and manages a SID and a key for connecting and reconnecting aclient communication session. A SID and a key can form a ticket as inthe type of ticket generated, validated and managed by the ticketauthority 6102 as described above. As such, in another embodiment, aticket may be used interchangeably for the combination of a sessionidentifier and a key.

The intermediary machine 30, as shown in FIG. 62, is configured tocommunicate with the ACR Service 5002. In one embodiment, the ACRService 5002 is configured to receive a request for a first SID and afirst key from the intermediary machine 30 and to thereafter generatethe first SID and first key. The ACR Service 5002 uses the first SID toidentify the communication session that is established between theclient machine 10 and a host service 4516. The first SID and the firstkey allow the client machine 10 to automatically reconnect with the hostservice 4516 after an abnormal disruption of service without requiringthe client machine 10 to provide authentication credentials again.

After generation of the first SID and the first key, the ACR Service5002 encrypts the authentication credentials supplied by the clientmachine 10 using the first key so that an attacker who gains access tothe intermediary machine 30 or the ACR Service 5002 cannot access theauthentication credentials without the first key. The ACR Service 5002then stores the encrypted authentication credentials with the SID inmemory 5018 and transmits the first SID and the first key to the clientmachine 10 over the network 150. Upon the client's receipt of the SIDand the key, the ACR Service 5002 destroys (i.e., deletes) the key fromits memory 5018.

In another embodiment, the first protocol service 4502 is configured togenerate a second SID and second key. The first protocol service 4502can also be configured to transmit the second SID and second key to theclient machine 10, while keeping a copy of the second SID and secondkey. The copy of the second SID and second key can later be used by thefirst protocol service 4502 to validate the second SID and second keyoriginally transmitted to the client machine 10 when it is laterpresented to the first protocol service 4502 during the process ofreconnecting the client machine 10. In one embodiment, the firstprotocol service 4502 transmits the second SID and second key to theclient machine 10 via the intermediary machine 30. In anotherembodiment, the first protocol service 4502 transmits the second SID andsecond key to the client machine 10 directly. Moreover, as described ingreater detail below, the first protocol service 4502 can be furtherconfigured to delete, during the process of reconnecting the clientmachine 10 to a host service 4516, the second SID and second key, andthereafter generate a replacement second SID and second key.Additionally, in another embodiment, the second SID and second key isconfigured for automatic deletion after a pre-determined period of time.

In one embodiment, the intermediary machine 30 serves as an intermediaryfor the first and second SIDs and keys. The intermediary machine 30receives, for example, the first SID and first key generated by the ACRService 5002 and the second SID and second key generated by the firstprotocol service 4502. The intermediary machine 30 can then transmit thefirst SID and first key and the SID and second key to the client machine10. Moreover, during the process of reconnecting the client machine 10to a host service 4516, the intermediary machine 30 can accept the firstSID and first key and the second SID and second key from the clientmachine 10 and thereafter transmit the first SID and first key to theACR Service 5002 and, if appropriate, the second SID and second key t tothe first protocol service 4502.

If the first communication session between the client machine 10 and thehost service 4516 terminates, for example abnormally, the new sessioncan be re-established without requiring the user to reenter his or herauthentication credentials. When the client machine 10 and the hostservice 4516 re-establish a second communication session, the clientmachine 10 transmits the first and second SIDs and keys to theintermediary machine 30. The intermediary machine 30 transmits the firstSID and first key to the ACR Service 5002, which uses the SID to locateand retrieve the encrypted authentication credentials for the firstconnection and uses the first key to decrypt the retrievedauthentication credentials. The ACR Service 5002 then authenticates theclient by validating the decrypted authentication credentials. Afterre-authentication, the second SID and second key is forwarded to thefirst protocol service 4502 to re-establish the second connection 4508with the host service 4516.

Referring to FIG. 63, another embodiment of a system 4500 for networkcommunications includes the networks 150 and 150′, the client machine10, the first protocol service 4502, the host services 4516, theintermediary machine 30, and the ticket authority 6102, as describedabove, and further depicts a first remote machine 30 and a second remotemachine 30, both of which are used, in one embodiment, for initiallyconnecting the client machine 10 to a host service 4516. Moreover, inthe embodiment of FIG. 63, the client machine 10 further includes a webbrowser 6302, such as, for example, the INTERNET EXPLORER program fromMicrosoft Corporation of Redmond, Wash., to connect to the World WideWeb.

In one embodiment (not shown), the system 4500 includes two or moreintermediary machines 30 and/or two or more first protocol services4502. The intermediary machine 30, through which messages between theclient machine 10 and the first protocol service 4502 must pass, and/orthe first protocol service 4502 can, as explained below, each be chosenbased on, for example, a load balancing equation.

Each of the first remote machine 30 and the second remote machine 30 canbe any computing device that is capable of communication and that hassufficient processor power and memory capacity to perform the operationsdescribed herein. For example, in one embodiment, the first remotemachine 30 is a web server, providing one or more websites or web basedapplications. In another embodiment, the second remote machine 30provides an XML service or web service.

In one embodiment, the client machine 10 and the network 150 form anexternal network 6304, separated from the rest of the system 6100 by afirst firewall 6306, depicted as a dashed line. The intermediary machine30 and the first remote machine 30 can be located in a “demilitarizedzone” 6308 (i.e., a network region placed between a company's privatenetwork and the public network), separated from the rest of the system4500 by the first firewall 6306 and a second firewall 6310, alsodepicted by a dashed line. In some embodiments, the first firewall 6306and the second firewall 6310 prohibit unauthorized communications to orfrom the remote machines 30. Then, as shown, the network 150′, the firstprotocol service 4502, the host services 4516 a-4516 n, the ticketauthority 6102, and the second remote machine 30, form an internalnetwork 6312, separated from the rest of the system 4500 by the secondfirewall 6310.

In some embodiments, the demilitarized zone 6308 includes a ticketprotocol service 6314 (shown in shadow in FIG. 63), comprising a proxy(not shown), and the first remote machine 30, which may be a web server.The proxy may comprise a security gateway through which messages overthe client-first protocol service communication channel 4504 pass. Inone embodiment, the network firewall 6306 repudiates any incomingmessage from the client-first protocol service communication channel4504 that does not have the first protocol service 4502 as itsdestination. Likewise, the network firewall 6306 repudiates any outgoingmessage for the client-first protocol service communication channel 4504unless its source is the first protocol service 4502. The securitygateway can alternatively be a router, firewall, relay, or any networkcomponent that can provide the necessary security. The proxy may also bea network component separate from the first protocol service 4502 thatmay run on the same computing device of the first protocol service 4502or on a different computing device. In some embodiments, the proxy is anintermediary for securely passing communications between the clientmachine 10 and the first protocol service 4502.

Alternatively, in another embodiment not shown in FIG. 63, the system4500 further includes a third remote machine 30 positioned, in thedemilitarized zone 6308, between the network 150 and the intermediarymachine 30. The third remote machine 30 can be any computing device thatis capable of networked communication and that has sufficient processorpower and memory capacity to perform the operations described herein. Asdescribed below, the third remote machine 30 is used, in someembodiments, during the process of initially connecting the clientmachine 10 to a host service 4516 and/or during the process ofreconnecting the client machine 10 to a host service 4516. Morespecifically, as described below, where the system 4500 includes two ormore intermediary machines 30, the third remote machine 30 can, based ona load balancing equation for example, choose the intermediary machine30 through with communications between the client agent 4506 of theclient machine 10 and the first protocol service 4502 must pass.

Moreover, referring to FIG. 63, the intermediary machine 30, in analternative embodiment, can be replaced by two or more levels “a”-“n” ofintermediary machines 30. As illustrated, each level “a”-“n” can includetwo or more intermediary machines 30′. As described below, the clientagent 4506 of the client machine 10 can be routed through anycombination of the intermediary machines 30 based on, for example, loadbalancing equations. For example, as illustrated, the client agent 4506can be routed through the intermediary machines 30 via connection 4504.For additional security, each of the “hops” via connection 4504 mayrequire a ticket or re-connection ticket for validating andauthenticating the multiple-hop connection between the client machine 10and the host service 4516. Other configurations of the system 4500, aswould be readily apparent to one skilled in the art, are also possible.

Referring again to FIG. 63, in one embodiment, the web browser 6302communicates over the network 150 with the first remote machine 30,which itself interfaces with the second remote machine 30 and the ticketauthority 6102. More specifically, the first remote machine 30 isconfigured with the address of the second remote machine 30 and theticket authority 6102. In one embodiment, as explained further below,the first remote machine 30 is configured to relay information between,and thereby prevent direct communication between, the web browser 6302of the client machine 10, the second remote machine 30, and the ticketauthority 6102. By preventing such direct communication, the firstremote machine 30 adds an additional level of security to the system4500. The first remote machine 30 can also be configured with theaddress of the intermediary machine 30, or, alternatively, with theaddress of two or more intermediary machines 30.

For its part, the second remote machine 30 is configured to determinewhich of the application programs running on the host services 4516 areavailable to a user of the client machine 10. In other words, the secondremote machine 30 is configured to determine which of the applicationprograms the user is authorized to access. In one embodiment, after theuser selects his desired application program, as described furtherbelow, the second remote machine 30 is further configured to determinewhich of the host services 4516 will be used to run the user's desiredapplication for purposes of load balancing. The second remote machine 30returns the address of that host service 4516 to the first remotemachine 30. The second remote machine 30 also returns the address of thefirst protocol service 4502, which can also be selected from amongst aplurality of first protocol services 4502 through the use of a loadbalancing equation, to the first remote machine 30. In turn, the firstremote machine 30 transmits the address of the chosen first protocolservice 4502 and the chosen host service 4516 to the ticket authority6102.

For its part, the ticket authority 6102 generates connection tickets. Inone embodiment, the ticket authority 6102 transmits an initialconnection ticket to the first remote machine 30 for transmission to theclient machine 10. In another embodiment, the ticket authority transmitsa first reconnection ticket to the intermediary machine 30.

In one embodiment, the ticket authority 6102 issues one or more ticketsto authenticate the client machine 10. In particular, the ticketauthority 6102 enables authentication of the client machine 10 over onecommunication channel (i.e., a client-web server communication channel)based on authentication credentials. The ticket authority 6102 furtherenables the client machine 10 to be authenticated to anothercommunication channel (i.e., the client-first protocol servicecommunication channel 4504) without having the client machine 10repeatedly provide authentication credentials on the other communicationchannel.

In one embodiment, the ticket authority 6102 is a stand-alone networkcomponent. In other embodiments, a modular ticket authority 136 is asoftware module residing on one or more remote machines 30. For example,there may be a ticket authority 6102 for each of the remote machines 30.In some embodiments, a first remote machine 30, such as a web server inthe demilitarized zone 6308, may communicate with the ticket authority6102 and/or the remote machine 30 over an agent-server communicationchannel. In another embodiment, the ticket authority 6102 may reside onan intermediary remote machine 30 separate from other remote machines30.

In one embodiment, the ticket authority 6102 generates a first ticketand a second ticket. In some embodiments, the tickets are both nonces.In further embodiments, the tickets are generated using a cryptographicrandom number generator that has been suitably seeded with randomness.The first ticket is transmitted to the client machine 10 and is used toestablish a first communication session between the client machine 10and the first protocol service 4502. The second ticket is transmitted tothe first protocol service 4502 and is used to establish a secondcommunication session between the first protocol service 4502 and aremote machine 30.

In some embodiments, the first remote machine 30 is a web server. In oneof these embodiments, the first remote machine 30 delivers web pages tothe client machine 10. In another of these embodiments, the first remotemachine 30 is capable of establishing a secure client-web servercommunication channel with the client machine 10.

In other embodiments, the first remote machine 30 is a web serverproviding a corporate portal, also referred to as an enterpriseinformation portal, to the client machine 10. In one of theseembodiments, enterprise portals are company web sites that aggregate,personalize and serve applications, data and content to users, whileoffering management tools for organizing and using information moreefficiently. In other embodiments, the first remote machine 30 providesa web portal, or Internet portal, to the client machine 10. A web portalis similar to a corporate portal but typically does not includebusiness-specific information.

In one embodiment, a user of the client machine 10 employs the webbrowser 6302 to authenticate the user to the first remote machine 30. Inone embodiment, the client machine 10 transmits user credentials, suchas log in and password information, to the first remote machine 30. Thefirst remote machine 30 verifies that the user has access to the machinefarm 38.

In a further embodiment, the web browser 6302 uses SSL to establish asecure client-web server communication channel. The web browser 6302 canalternatively connect to the first remote machine 30 over a client-webserver communication channel using other security protocols, such as,but not limited to, Secure Hypertext Transfer Protocol (SHTTP) developedby Terisa Systems of Los Altos, Calif., HTTP over SSL (HTTPS), PrivateCommunication Technology (PCT) developed by Microsoft Corporation ofRedmond, Wash., and the Transport Level Security (TLS) standardpromulgated by the Internet Engineering Task Force (IETF). In oneembodiment, the first remote machine 30 transmits a web portal orenterprise portal, as described above, to the client machine 10 uponvalidation of the user to enable the client machine 10 to request aresource, such as, for example, an application or a server desktop to beremotely displayed on the client machine 10.

The client-web server communication channel may be any securecommunication channel. In some embodiments, communications over thechannel are encrypted. In certain of these embodiments, the clientmachine 10 and the first remote machine 30 may communicate using theSecure Socket Layer (SSL) of the HyperText Transfer Protocol (HTTPS).Alternatively, the client machine 10 and the first remote machine 30 mayuse other encryption techniques, such as symmetric encryptiontechniques, to protect communications.

Further, in one embodiment the client-first protocol servicecommunication channel 4502 can be established by using, for example, apresentation services protocol such as ICA, X11 protocol, VNC, or RDP.Although described as establishing a first communication session betweenthe client machine 10 and the first protocol service 4502 and a secondcommunication session between the first protocol service 4502 and theremote machine 30, the communication session can be viewed as a single,logical communication session between the client machine 10 and the hostservice 4516.

In another embodiment of a network communication system 4500 as shown inFIG. 64, the ACR Service 5002 can be used instead of the ticketauthority 6102 to reconnect a client machine 10 to a host service 4516.Instead of using tickets as with the ticket authority 6102, the ACRService 5002 generates, validates and manages SIDs and keys forconnecting and reconnecting client communication sessions. The ACRService 5002 authenticates and re-authenticates the client to a hostservice 4516 or remote machine 30 using a SID and key, or a ticket,associated with the client machine 10. As previously mentioned, a ticketcan be used to refer to the combination of a SID and key or a ticket cancomprise a SID and a key.

The system 4500 of FIG. 64 includes the networks 150 and 150′, theclient machine 10, the first protocol service 4502, the host services4516, the intermediary machine 30, and the ACR Service 5002, asdescribed above, and further depicts a first remote machine 30 and asecond remote machine 30, both of which are used, in one embodiment, forinitially connecting the client machine 10 to a host service 4516.Moreover, the client machine 10 further includes a web browser 6302 toconnect to the World Wide Web.

In one embodiment (not shown), the system 4500 includes two or moreintermediary machines 30 and/or two or more first protocol services 4502or two or more ACR Services 5002. The intermediary machine 30, throughwhich messages between the client machine 10 and the first protocolservice 4502 must pass, and/or the first protocol service 4502 canand/or the ACR Service 5002, as explained below, each be chosen basedon, for example, a load balancing equation.

In another embodiment, the system 4500 of FIG. 64 can include anexternal network 6304, separated from a “demilitarized zone” 6308 by afirst firewall 6306 which in turn is separated from an internal network6312 by a second firewall 6310. Although the invention is discussedabove in terms of various network topologies in FIGS. 63 and 64, anyother network topologies can be used, such as for example, a topologyincluding combinations of internal networks, external networks,sub-networks, intranets, firewalls, security zones, single servers, aserver network or server farms.

Alternatively, in another embodiment not shown in FIG. 64, the system4500 further includes a third remote machine 30 positioned, in thedemilitarized zone 6308, between the network 150 and the intermediarymachine 30. The third remote machine 30 is used, in some embodiments,during the process of initially connecting the client machine 10 to ahost service 4516 and/or during the process of reconnecting the clientmachine 10 to a host service 4516.

In another embodiment of the system 4500 in FIG. 64, the intermediarymachine 30, can be replaced by two or more levels “a”-“n” ofintermediary machines 30′. The client agent 4506 of the client machine10 can be routed through any combination of the intermediary machines 30based on, for example, load balancing equations.

In one embodiment, the web browser 6302 communicates over the network150 with the first remote machine 30, which itself interfaces with thesecond remote machine 30 and the ACR Service 5002. The first remotemachine 30 is configured with the address of the second remote machine30 and the ACR Service 5002. In another embodiment to provide anadditional level of security in the system 4500, the first remotemachine 30 is configured to relay information between, and therebyprevent direct communication between, the web browser 6302 of the clientmachine 10, the second remote machine 30, and the ACR Service 5002. Thefirst remote machine 30 can also be configured with the address of anyof the intermediary machines 30′.

For its part, the second remote machine 30 is configured to determinewhich of the application programs running on the host services 4516 areavailable to a user of the client machine 10 and to provide the addressof the host service 4516 selected by the user to the first remotemachine 30. The second remote machine 30 also provides the address ofone of the multiple first protocol service 4502, through the use of aload balancing equation, to the first remote machine 30. In turn, thefirst remote machine 30 transmits the address of the chosen firstprotocol service 4502 and the chosen host service 4516 to the ACRService 5002.

For its part, the ACR Service 5002 generates, validates and managesconnection SIDs and key to provide authentication and re-authenticationsservices to re-establish a client's communication session with a hostservice 4516 or remote machine 30, as described herein. In oneembodiment, the ACR Service 5002 transmits a first SID and first key tothe first remote machine 30 for transmission to the client machine 10.In another embodiment, the ACR Service 5002 transmits a first SID andfirst key to one of the intermediary machines 30.

In other embodiments, methods for network communications enablereconnecting a client machine 10 to a host service 4516 using aplurality of secondary protocols encapsulated within a first protocol.The method includes establishing a first connection between a clientmachine 10 and a first protocol service 4502 using a first protocol andcommunicating between the client machine 10 and the first protocolservice 4502 via a plurality of second protocols encapsulated within thefirst protocol. Moreover, at least one of the second protocols includesa plurality of virtual channels.

In one embodiment of this aspect of the invention, a second connectionis established between the first protocol service 4502 and a hostservice 4516 using one of the secondary protocols. Communication betweenthe first protocol service 4502 and the host service 4516 occurs via oneof the secondary protocols. Specifically, each of the plurality ofsecond connections is established between the first protocol service4502 and a different host service 4516 and each of the plurality ofsecond connections is established using one of the plurality ofsecondary protocols. In yet another embodiment, the first connectionbetween the client machine 10 and the first protocol service 4516 isestablished through one or more intermediary machines 30.

Referring now to FIG. 65, one embodiment of a method 6500 forreconnecting a client to a host service after a network failure isillustrated. At step 6502, the client machine 10 initially connects toone of a plurality of host services 4516. Generally, the client machine10 is required to transmit authentication credentials to the hostservice 4516 to initiate the communication session. After the clientmachine 10 is connected to the host service 4516, the client machine 10and the host service 4516 communicate, through the first protocolservice 4502, and at step 6504, via a plurality of secondary protocolsencapsulated within the first protocol as discussed above in referenceto FIGS. 47-48 and FIG. 49. In one embodiment, the first protocolservice 4502 encrypts, prior to the transmission of any first protocolpackets, communications at the level of the first protocol 4704, therebysecuring the communications. In another embodiment, the first protocolservice 4502 compresses, prior to the transmission of any first protocolpackets, the communications at the level of the first protocol, therebyimproving communication efficiency.

At step 6506, the client agent 4506 determines whether the connection4504 between the client agent 4506 and the first protocol service 4502has failed. For example, the connection 4504 a between the client agent4506 and the intermediary machine 30 may have failed, the connection4504 b between the intermediary machine 30 and the first protocolservice 4502 may have failed, or both the connection 4504 a and theconnection 4504 b may have failed. If the client agent 4506 determinesthat the connection 4504 has not failed, the method 6500 proceeds tostep 6508. If, on the other hand, the client agent 4506 determines thatthe connection 4504 has failed, the client machine 10 is, at step 6510,reconnected to the host service 4516.

The step of reconnecting in step 6510 after a first communicationsession ends abnormally, can comprise in a system 4500 deploying aticket authority 6102 and the client machine 10 transmitting the SID andthe first and second reconnection tickets to the intermediary machine30. The intermediary machine 30 uses the first reconnection ticket toauthenticate the client machine 10 and re-establish the connection 4504between the client machine 10 and the intermediate node 30′. Theintermediary machine 30 then transmits the second reconnection ticket tothe first protocol service 4502, which uses the second reconnectionticket to authenticate re-establish the connection 4508 to the hostservice 4516. The reconnection tickets thus allow the client machine 10to automatically establish a second communication session to the hostservice 4516 without retransmitting the authentication credentials asecond time.

In another embodiment, the step of reconnecting, in step 6510, can alsocomprise a system 4500 deploying an ACR Service 5002. In such anembodiment, the client machine 10 transmits a first SID and first key tothe intermediary machine 30 to authenticate the client machine 10 andreestablish the connection of the client machine 10 to the host service4516.

It is determined, at step 6508, whether the client machine 10 wishes tocleanly terminate its connection 4504 with the first protocol service4502 and, consequently, its connections 4508 a-4508 n with the hostservices 4516 a-4516 n. If not, communication between the client machine10 and the first protocol service 4502, via the plurality of secondaryprotocols encapsulated within the first protocol, continues at step6504. If so, then, at step 6512, all connections 4504 a, 4504 b, and4508 a-4508 n are broken and all reconnection tickets are deleted. Inanother embodiment using an ACR Service 5002, at step 6512, allconnections 4504 a, 4504 b, and 4508 a-4508 n are broken and all SIDSand keys are deleted. In one embodiment, the intermediary machine 30uses a handle it receives from the ticket authority 6102 to delete acopy of a first reconnection ticket kept at the ticket authority 6102.In another embodiment deploying a ticket authority 6102, the firstprotocol service 4502 deletes a copy of a second reconnection ticketkept at the first protocol service 4502. In yet another embodimentdeploying the ACR Service 5002, the first protocol service 4502 deletesa copy of a second SID and second key kept at the first protocol service4502.

In a further embodiment using a ticket authority 6102, if for somereason a secondary protocol connection 4508 fails, a copy of the secondreconnection ticket associated therewith and kept at the first protocolservice 4502 is deleted by the first protocol service 4502. In yetanother embodiment, a first reconnection ticket and/or a secondreconnection ticket is automatically deleted after a pre-determinedperiod of time following a failure in the connection 4504, as at step6506, and/or following a clean termination of the connection 4504, as atstep 6508.

In another aspect, this invention relates to methods for reconnectingthe client machine 10 to the host service 4516 using the ACR Service5002. Referring now to FIG. 66, one embodiment of step 6510 in FIG. 65is illustrated. The client machine 10 transmits the first SID and thefirst key to the ACR Service 5002 to reconnect to the host service (step6602). The ACR Service 5002 uses the SID (step 6604) to locate andretrieve the encrypted authentication credentials and uses the key (step6606) to decrypt the retrieved authentication credentials. In oneembodiment (not shown), the ACR Service 5002 uses the decryptedauthentication credentials to re-authenticate the client machine 10 tothe maintained session between the first protocol service 4502 and thehost service 4516. After re-authenticating, the reestablished connectionof the client machine 10 to the first protocol service 4516 is re-linkedto the maintained session between the first protocol service 4502 andthe host service 4516.

In another embodiment, during the second communication session, the ACRService 5002 generates (step 6608) a second key for the authenticationcredentials and then encrypts (step 6610) the authentication credentialsusing the second key. The ACR Service 5002 creates a second SID (step6612). Then the decrypted authentication credentials arere-authenticated with the host service 4516 and the second SID isassociated with the maintained communication session with the hostservice 4516 (step 6612 a). The ACR Service 5002 then transmits thesecond SID and second key to the client machine 10 (step 6614). In oneembodiment, the ACR Service 5002 may transmit the second SID and secondkey through an intermediary machine 30. The client machine 10 stores thesecond SID and second key (step 6616). The ACR Service 5002 then deletesthe second key (step 6618).

Referring to FIGS. 67-68, one embodiment of a method 6700 for initiallyconnecting the client machine 10 to the host service 4516 using an ACRService 5002 is illustrated. At step 6702, the client machine 10, usingthe browser 6302, sends a request, such as, for example, an HTTPrequest, to the first remote machine 30. The first remote machine 30returns a web page, such as, for example, an HTML form requestingauthentication information (e.g., a username and a password). A user ofthe client machine 10 enters his authentication credentials andtransmits the completed form to the first remote machine 30.

The first remote machine 30, at step 6704, then informs the user of theclient machine 10 of applications available for execution. In oneembodiment, the first remote machine 30 extracts the user's credentialsfrom the login page and transmits them to the second remote machine 30,together with a request for the second remote machine 30 to enumeratethe applications available to the user. Based on the user's credentials,the second remote machine 30 returns a list of specific applicationsavailable to the first remote machine 30, which then forwards the list,in the form of a web page for example, to the user of the client machine10.

At step 6706, the user selects the desired application and a request forthat application is sent to the first remote machine 30. For example, inone embodiment, the user clicks on a desired application listed in theweb page presented to him by the first remote machine 30 and an HTTPrequest for that application is forwarded to the first remote machine30. The request is processed by the first computing node 140 andforwarded to the second remote machine 30.

At step 6708, the second remote machine 30 determines the host service4516 on which the desired application will be executed. The secondremote machine 30 can make that determination based, for example, on aload balancing equation. In one embodiment, the second remote machine 30also determines a first protocol service 4502 from amongst a pluralityof first protocol services 4502 that will be used to communicate withthe host service 4516 via a connection 4508. Again, the second remotemachine 30 can make that determination based, for example, on a loadbalancing equation. The second remote machine 30 returns the address ofthe chosen host service 4516 and the chosen first protocol service 4502to the first remote machine 30.

The client machine 10, at step 6710, is then provided with an initialconnection session id and key, a first SID and first key, and an addressfor the intermediary machine 30 (which is either its actual address orits virtual address, as described below). In one embodiment, the firstremote machine 30 provides the address for the chosen host service 4516and the chosen first protocol service 4502 to the ACR Service 5002,together with a request for the initial connection session ID and key.The ACR Service 5002 generates the initial session ID and key, andtransmits the session ID and key to the first remote machine 30, whilekeeping a copy for itself.

In some embodiments, the ticket authority 6102 generates an initialconnection ticket. In one of these embodiments, the ticket authority6102 keeps the address of the chosen host service 4516 and the chosenfirst protocol service 4502, generates the initial connection ticket,and transmits the initial connection ticket to the first remote machine30, while keeping a copy for itself. In one embodiment, the ticketauthority 6102, in response to the request for the initial connectionticket by the first remote machine 30, generates connection tickets foreach of the “hops” between the client machine 10 and the host service4516. In another embodiment, the first remote machine 30 requestsinitial connection tickets for each of the “hops” either in a singlerequest or in multiple requests.

The first remote machine 30, configured, in one embodiment, with theactual address of the intermediary machine 30, then transmits the actualaddress of the intermediary machine 30 and the initial connectionsession ID and key to the browser 6302 of the client machine 10. In someembodiments, an initial connection ticket is transmitted. The firstremote machine 30 can, for example, first create a file containing boththe actual address of the intermediary machine 30 and the initialconnection ticket and then transmitting the file to the browser 6302 ofthe client machine 10. Optionally, in another embodiment, the firstremote machine 30 is configured with the actual address of two or moreintermediary machines 30. In such an embodiment, the first remotemachine 30 first determines the intermediary machine 30 through whichmessages between the client machine 10 and the first protocol service4502 will have to pass. The first remote machine 30 then transmits theactual address of that chosen intermediary machine 30 and the initialconnection ticket to the browser 6302 of the client machine 10 using,for example, the file described above. In one embodiment, the firstremote machine 30 chooses the intermediary machine 30 using a loadbalancing equation. The client agent 4506 of the client machine 10 isthen launched and uses the address of the intermediary machine 30, toestablish, at step 6712, a first protocol connection 4504 a between theclient agent 4506 of the client machine 10 and the intermediary machine30.

Alternatively, in another embodiment, the first remote machine 30 isconfigured with an actual address of the third remote machine 30, whichserves as a virtual address of an intermediary machine 30. In such anembodiment, the first remote machine 30 transmits, at step 6710, theactual address of the third remote machine 30 and the initial connectionsession ID and key to the browser 6302 of the client machine 10 using,for example, the file described above. The client agent 4506 of theclient machine 10 is then launched and uses the actual address of thethird remote machine 30 to establish, at step 6712, a first protocolconnection between the client agent 4506 of the client machine 10 andthe third remote machine 30. The third remote machine 30 then determinesthe intermediary machine 30 through which messages between the clientmachine 10 and the first protocol service 4502 will have to pass. In oneembodiment, the third remote machine 30 chooses the intermediary machine30 using a load balancing equation. Having chosen the intermediarymachine 30, the third remote machine 30 establishes a first protocolconnection to the intermediary machine 30. A first protocol connection4504 a therefore exists, through the third remote machine 30, betweenthe client agent 4506 of the client machine 10 and the intermediarymachine 30. The actual address of the third remote machine 30 istherefore mapped to the actual address of the intermediary machine 30.To the client agent 4506 of the client machine 10, the actual address ofthe third remote machine 30 therefore serves as a virtual address of theintermediary machine 30.

In one embodiment, where more than one level of intermediary machines30′ exist, as described above, the first remote machine 30 or the thirdremote machine 30, respectively, only choose the intermediary machine 30to which the client agent 4506 will connect at level “a.” In such anembodiment, at each of the levels “a”-“n−1”, the intermediary machine 30through which the client agent 4506 is routed at that level thereafterdetermines, based on a load balancing equation for example, theintermediary machine 30 to which it will connect at the next level.Alternatively, in other embodiments, the first remote machine 30 or thethird remote machine 30, respectively, determine, for more than one orall of the levels “a”-“n”, the intermediary machines 30 through whichthe client agent 4506 will be routed.

Having established the first protocol connection 4504 a between theclient agent 4506 of the client machine 10 and the intermediary machine30, for example the intermediate node 30′ at level “n” (hereinafterreferred to in method 6700 as the intermediary machine 30), the clientagent 4506 then transmits the initial connection ticket to theintermediary machine 30.

It is then determined, at step 6714, whether the initial connection SIDand key is valid. In one embodiment, the intermediary machine 30transmits the initial connection SID and key to the ACR Service 5002 forvalidation. In one embodiment, the ACR Service 5002 validates the SIDand key by comparing it to the copy of the SID and encryptedauthentication credentials it kept at step 6710. If the ACR Service 5002determines the SID and key to be valid, the ACR Service 5002 transmits,at step 6802 (FIG. 68), the address of the first protocol service 4502and the address of the chosen host service 4516 to the intermediarymachine 30. The first protocol service 4502 can also delete the SID andkey and any copy thereof. If, on the other hand, the ACR Service 5002determines the SID and key to be invalid, the client machine 10 is, atstep 6716, refused connection to the first protocol service 4502 and,consequently, connection to the host service 4516. In some embodiments,the ticket authority 6102 receives an initial connection ticket from theintermediary machine 30 for validation and validates the ticket asdescribed above.

Following step 6802, the intermediary machine 30 uses the address of thechosen first protocol service 4502 to establish, at step 6804, a firstprotocol connection 4504 b between the intermediary machine 30 and thefirst protocol service 4502. In one embodiment, the intermediary machine30 uses an initial connection ticket to establish the first protocolconnection 4504 b between the intermediary machine 30 and the firstprotocol service 4502. In one case, the intermediary machine 30 uses thesame initial connection ticket received from the client machine 10 tovalidate the connection 4504 b. In another case, the intermediarymachine 30 uses an initial connection ticket generated for and valid forthe first protocol connection 4504 b. A first protocol connection 4504therefore now exists, through the intermediary machine 30, between theclient agent 4506 of the client machine 10 and the first protocolservice 4502. The intermediary machine 30 can also pass the address ofthe chosen host service 4516 to the first protocol service 4502.

In one embodiment, at step 6806, the first protocol service 4502 usesthe address of the chosen host service 4516 to establish a secondaryprotocol connection 4508 between the first protocol service 4502 and thechosen host service 4516. For example, the chosen host service 4516 isin fact the host service 4516 a and a secondary protocol connection 4508a is established between the first protocol service 4502 and the hostservice 4516 a.

In one embodiment, following step 6806, the user chooses, at step 6808,a second application to be executed and the second remote machine 30determines, at step 6810, the host service 4516 on which the secondapplication is to be executed. For example, by calculating a loadbalancing equation, the second remote machine 30 may choose the hostservice 4516 b to execute the second application program. The secondremote machine 30 then transmits the address of the chosen host service4516 b to the first protocol service 4502. In one embodiment, the secondremote machine 30 is in direct communication with the first protocolservice 4502 and directly transmits the address thereto. In anotherembodiment, the address of the chosen host service 4516 b is indirectlytransmitted to the first protocol service 4502. For example, the addresscan be transmitted to the first protocol service 4502 through anycombination of the first remote machine 30, the ACR Service 5002, theintermediary machine 30, and the first protocol service 4502. Havingreceived the address of the chosen host service 4516 b, the firstprotocol service 4502 establishes, at step 6812, a secondary protocolconnection 4508 b between the first protocol service 4502 and the chosenhost service 4516 b.

The secondary protocols that can be used to communicate over theconnections 4508 a and 4508 b include, but are not limited to, HTTP,FTP, Oscar, Telnet, ICA, and RDP. Moreover, in one embodiment, at leastone of the secondary protocols, as described above, includes a pluralityof virtual channels, each of which can include a plurality of protocolpackets enabling functionality at the client machine 10. For example, inone embodiment, one host service 4516 a is a web server, communicatingwith the first protocol service 4502 over the connection 4508 a usingthe HTTP protocol, and another host service 4516 b is an applicationserver, communicating with the first protocol service 4502 over theconnection 4508 b using the ICA protocol. The host service 4516 bgenerates both protocol packets for transmitting graphical screencommands to the client machine 10, for causing the client machine 10 todisplay a graphical user interface, and protocol packets fortransmitting printer commands to the client machine 10, for causing adocument to be printed at the client machine 10.

Steps 6808, 6810, and 6812 can be repeated any number of times. As such,any number of application programs can be executed on any number of hostservices 4516 a-4516 n, the outputs of which can be communicated to thefirst protocol service 4502 over the connections 4508 a-4508 n using anynumber of secondary protocols.

Turning now to step 6814, the first protocol service 4502 can, asdescribed above, encapsulate the plurality of secondary protocols withinthe first protocol. As such, the client machine 10 is connected to, andsimultaneously communicates with, a plurality of host services 4516.

In another embodiment, prior to performing steps 6808, 6810, and 6812 toexecute a new application program on a host service 4516, such as, forexample, the host service 4516 b, a user of the client machine 10 endsexecution of another application program, such as, for example, anapplication program executing on host service 4516 a. In such a case,the first protocol service 4502 disrupts the connection 4508 a betweenthe first protocol service 4502 and the host service 4516 a. The firstprotocol service 4502 then establishes, by implementing steps 6808,6810, and 6812, the connection 4508 b between the first protocol service4502 and the host service 4516 b, without interrupting the connection4504 between the client machine 10 and the first protocol service 4502.

In one embodiment, a first SID and key is generated at step 6816. Insome embodiments, a first re-connection ticket is generated. Forexample, the intermediary machine 30 requests a first SID and key fromthe ACR Service 5002. Upon receiving the request, the ACR Service 5002generates the first SID and key, and can also generate a handle, whichis, for example, a random number. The ACR Service 5002 can thentransmit, at step 6902, the first SID and key and the handle to theintermediary machine 30, while keeping a copy of the first SID and keyand a copy of the handle. The ACR Service 5002 continues to maintain theaddress of the first protocol service 4502 that was transmitted to it bythe first remote machine 30 at step 6710. The intermediary machine 30then transmits, at step 6904, the first reconnection ticket to theclient machine 10.

In some embodiments, the intermediary machine 30 requests a firstre-connection ticket from the ticket authority 6102 or requests a firstre-connection ticket for each of the “hops” between the client machine10 and the host service 4516. Upon receiving the request, the ticketauthority 6102 generates the one or more first re-connection tickets. Are-connection ticket is, for example, a large random number, and canalso generate a handle, which is, for example, a smaller random number.The ticket authority 6102 can then transmit, at step 6902, the firstre-connection tickets and the handles to the intermediary node 632,while keeping a copy of the first re-connection tickets and a copy ofthe handles. The ticket authority 6102 continues to maintain the addressof the first protocol service 4502 that was transmitted to it by thefirst remote machine 30 at step 6710. The intermediary node 632 thentransmits, at step 6904, the client's first re-connection ticket to theclient machine 10.

At step 6906, a second SID and key is then generated. In one embodiment,the first protocol service 4502 generates the second SID and key. Thefirst protocol service 4502, at step 6908, then transmits the second SIDand key, through the intermediary machine 30, to the client machine 10.In doing so, the first protocol service 4502 keeps a copy of the key anda session number associated therewith for identifying the session to bereconnected following a disruption of the connection 4504. In oneembodiment, for example, the first protocol service 4502 maintains, fora particular session number, a table listing the secondary protocolconnections 4508 a-4508 n associated with that session number.

At step 6906, one or more second re-connection tickets are thengenerated. In one embodiment, the first protocol service 4502 generatesthe second re-connection ticket for the client machine 10, which can be,for example, a large random number. In another embodiment, the firstprotocol service 4502 generates second re-connection tickets for one ormore of the “hops” between the client machine 10 and the host service4516. The first protocol service 4502, at step 6908, then transmits theclient's second re-connection ticket, through the intermediary machine30, to the client machine 10. In doing so, the first protocol service4502 keeps a copy of the second re-connection ticket and a sessionnumber associated therewith for identifying the session to bere-connected following a disruption of the connection 4504. In oneembodiment, for example, the first protocol service 4502 maintains, fora particular session number, a table listing the secondary protocolconnections 4508 a-4508 n associated with that session number. In a likemanner, the first protocol service 4502 may maintain the first and/orsecond re-connection tickets for each of the “hops” being validated toreconnect the client machine 10 to the host service 4516.

Accordingly, following re-establishment of the first protocol connection4504 and validation of the second SID and key at the first protocolservice 4502, or second re-connection ticket, as described below, thefirst protocol service 4502 can identify the secondary protocolconnections 4508 to be encapsulated within the re-established firstprotocol connection 4504 for communication to the client machine 10.

In an embodiment not shown in FIGS. 67-69, a ticket authority 6102 canbe used instead of the ACR Service 5002 to provide for reconnecting aclient machine 10 to a host service 4516. In the method 6700, the ticketauthority 6102 would generate and transmit reconnection tickets insteadof SIDs and keys as with the ACR Service 5002. For example, at step6710, a ticket authority 6102 would provide the client machine 10 withan initial connection ticket and an address for the intermediary machine30. Also, in step 6714, the ticket authority 6102 would determine if theinitial connection ticket is valid and at step 6816, would generate afirst reconnection ticket. Additionally, at steps 6902, 6904, 6906 and6908 the ticket authority would generate and transmit the first andsecond reconnection tickets in accordance with method 6700. As such, theticket authority 6102 facilitated the reconnecting of the client machine10 to the host service 4516.

Referring now to FIG. 70, one embodiment of a method 7000 for providinga client machine 10 with a persistent and reliable connection to one ormore host services 4516 and for reconnecting the client machine 10 tothe host services 4516 (for example at step 6510 of FIG. 65) isillustrated. In particular, at step 7002, the secondary protocolconnection 4508 between the first protocol service 4502 and each of theone or more host services 4516 is maintained. Moreover, at step 7004, aqueue of data packets most recently transmitted between the client agent4506 of the client machine 10 and the first protocol service 4502, viathe connection 4504 that was determined to have broken, for example, atstep 6510 of FIG. 65, is maintained. In one embodiment, the data packetsare queued and maintained both before and upon failure of the connection4504. The queued data packets can be maintained, for example, in abuffer by the client agent 4506. Alternatively, the first protocolservice 4502 can maintain in a buffer the queued data packets. In yetanother embodiment, both the client agent 4506 and the first protocolservice 4502 maintain the queued data packets in a buffer.

At step 7006, a new first protocol connection 4504 is establishedbetween the client agent 4506 of the client machine 10 and the firstprotocol service 4502 and linked to the maintained secondary protocolconnection 4508 between the first protocol service 4502 and each of theone or more host services 4516, thereby reconnecting the client machine10 to the host services 4516. After the client machine 10 isreconnected, the queued data packets maintained at step 7004 can betransmitted, at step 7008, via the newly established first protocolconnection 4504. As such, the communication session between the hostservices 4516 and the client machine 10, through the first protocolservice 4502, is persistent and proceeds without any loss of data. Inone embodiment, the ACR Service 5002 authenticates the client machine 10to the host service 4516 before reconnecting the client machine 10 to ahost service 4516. In another embodiment, the first protocol service4502 validates a reconnection ticket with the ticket authority 6102before reconnecting the client machine 10 to a host service 4516.

In an embodiment with multiple “hops” traversing multiple first protocolservices 4502, a portion or all of the data packets may be maintained atone or more of the first protocol services 4502 so that each “hop” maybe re-established. After the client machine 10 is re-connected andre-linked to the first of the one or more first protocol services 4502as described above, each of the remaining connections may bere-established and re-linked to the previously re-linked “hop” until thefinal “hop” to the host service 4516 is re-established. Either after thefinal “hop” is re-established and re-linked, or as each “hop” isre-established and re-linked, the queued data packets maintained can betransmitted.

FIGS. 71-72, illustrate one embodiment of a method 7100 for reconnectingthe client machine 10 to the one or more host services 4516 using an ACRService 5002 as in the embodiment of the system 4500 depicted in FIG.64.

At step 7102, any remaining connections between the client machine 10and the first protocol service 4502 are broken. For example, where theconnection 4504 a has failed, but the connection 4504 b has not, theconnection 4504 b is broken. Alternatively, where the connection 4504 bhas failed, but the connection 4504 a has not, the connection 4504 a isbroken.

In one embodiment, using the actual address of the intermediary machine30 provided to the client machine 10, the client agent 4506 of theclient machine 10 then re-establishes, at step 7104, the first protocolconnection 4504 a between the client agent 4506 and the intermediarymachine 30. Alternatively, in another embodiment, using the actualaddress of the third remote machine 30 provided to the client machine10, the client agent 4506 of the client machine 10 then re-establishes,at step 7104, a first protocol connection between the client agent 4506and the third remote machine 30. The third remote machine 30 thendetermines the intermediary machine 30 through which messages betweenthe client machine 10 and the first protocol service 4502 will have topass. In one embodiment, the third remote machine 30 chooses theintermediary machine 30 using a load balancing equation. Theintermediary machine 30 chosen by the third remote machine 30 inreconnecting the client machine 10 to the one or more host services 4516can be different from that chosen to initially connect the clientmachine 10 to the one or more host services 4516. In one embodiment, aninitial connection ticket for the chosen intermediary machine 30 isgenerated when re-connecting the client machine 10 to a host service4516.

Having chosen the intermediary machine 30, the third remote machine 30re-establishes a first protocol connection to the intermediary machine30. A first protocol connection 4504 a is therefore re-established,through the third remote machine 30, between the client agent 4506 ofthe client machine 10 and the intermediary machine 30. In oneembodiment, when the first protocol connection 4504 to the intermediarymachine 30 is re-established, the first protocol connection 4504 isvalidated by validating a first or second re-connection ticket for this“hop” with the ticket authority 6102.

In one embodiment, where more than one level of intermediary machines 30exist, the intermediary machine 30 through which the client agent 4506is routed at each of the levels “a”-“n−1” thereafter determines, basedon a load balancing equation for example, the intermediary machine 30 towhich it will connect at the next level. Alternatively, in anotherembodiment, the third remote machine 30 determines, for more than one orall of the levels “a”-“n”, the intermediary machines 30 through whichthe client agent 4506 will be routed. In other embodiments, either theintermediary machine 30 or one of the remote machines 30 (e.g., thethird remote machine 30) generates first or second re-connection ticketsfor one or more of the connections or “hops” through which the clientagent 4506 is routed.

Having re-established the first protocol connection 4504 a between theclient agent 4506 of the client machine 10 and the intermediary machine30, for example the intermediate node 30′ at level “n” (hereinafterreferred to in method 7100 as the intermediary machine 30), the clientagent 4506 then transmits, at step 7106, the first SID and key and thesecond SID and key to the intermediary machine 30. In one embodiment,the client agent 4506 transmits, at step 7106, the first re-connectionticket and the second re-connection ticket for the client machine 10 tothe intermediary machine 30.

It is then determined, at step 7108, whether the first SID and key isvalid. In one embodiment, the validity of the first SID and key isdetermined by using the ACR Service 5002. For example, the intermediarymachine 30 transmits the first SID and key to the ACR Service 5002. Inone embodiment, the ACR Service 5002 determines the validity of thefirst SID and key by comparing it to a copy of the first SID stored inmemory 5018. If the ACR Service 5002 determines the first SID and key tobe valid, the ACR Service 5002 re-authenticates the client machine 10 tothe host service 4516 and transmits, at step 7110, the address of thefirst protocol service 4502 to the intermediary machine 30. Otherwise,if the ACR Service 5002 determines the first SID and key to be invalid,the client machine 10 is, at step 7112, refused reconnection to thefirst protocol service 4502 and, consequently, reconnection to the hostservices 4516.

In one embodiment, the validity of a first re-connection ticket isdetermined by using the ticket authority 6102. For example, theintermediary machine 30 transmits the first re-connection ticket to theticket authority 6102. In one embodiment, the ticket authority 6102determines the validity of the first re-connection ticket by comparingit to a previously kept copy of the first re-connection ticket. If theticket authority 6102 determines the first re-connection ticket to bevalid, the ticket authority 6102 transmits, at step 7110, the address ofthe first protocol service 4502 to the intermediary machine 30.Otherwise, if the ticket authority 6102 determines the firstre-connection ticket to be invalid, the client machine 10 is, at step7112, refused re-connection to the first protocol service 4502 and,consequently, re-connection to the host services 4516.

At step 7114, the first SID and key is deleted by, for example, the ACRService 5002 and a replacement second SID and key is generated by theACR Service 5002. In some such embodiments, the ACR Service 5002transmits the second SID and key to the intermediary machine 30. In someembodiments, the ACR Service 5002 waits for the client machine 10 toacknowledge that it has received the second SID and key before itproceeds to delete the first SID and key.

In other embodiments, at step 7114, a first re-connection ticket isdeleted by, for example, the ticket authority 6102 and a replacementfirst re-connection ticket is generated by, for example, the ticketauthority 6102. Moreover, a replacement handle can be generated by, forexample, the ticket authority 6102. In some such embodiments, the ticketauthority 6102 transmits the replacement first re-connection ticket andthe replacement handle to the intermediary machine 30. Moreover, in somesuch embodiments, the ticket authority 6102 keeps a copy of thereplacement first re-connection ticket. In some embodiments, the ticketauthority 6102 waits for the client machine 10 to acknowledge that ithas received the replacement first re-connection ticket before itproceeds to delete the first re-connection ticket.

After the first SID and key (or, in some embodiments, the firstre-connection ticket) is validated, the intermediary machine 30, usingthe address of the first protocol service 4502, re-establishes, at step7116, the first protocol connection 4504 b between the intermediarymachine 30 and the first protocol service 4502. Having re-establishedthe first protocol connection 4504 b between the intermediary machine 30and the first protocol service 4502, it is then determined whether thesecond SID and key, or re-connection ticket, is valid.

In one embodiment, the validity of the second SID and key is determinedby using the first protocol service 4502. For example, the intermediarymachine 30 transmits the second SID and key to the first protocolservice 4502. In one embodiment, the first protocol service 4502determines the validity of the second SID and key by comparing it to apreviously kept copy of the second SID and encrypted authenticationcredentials. If the first protocol service 4502 determines the secondSID and key to be valid, the re-established first protocol connection4504 b between the first intermediary machine 30 and the first protocolservice 4502 is linked, at step 7202, to the maintained secondaryprotocol connection 4508 between the first protocol service 4502 andeach of the one or more host services 4516. Otherwise, if the firstprotocol service 4502 determines the second SID and key to be invalid,the re-established first protocol connection 4504 b is not linked to theone or more maintained secondary protocol connections 4508 and theclient machine 10 is refused reconnection to the one or more hostservices 4516.

In embodiments using re-connection tickets, the validity of the secondre-connection ticket is determined by using the first protocol service4502. For example, the intermediary machine 30 transmits the secondre-connection ticket to the first protocol service 4502. In oneembodiment, the first protocol service 4502 determines the validity ofthe second re-connection ticket by comparing it to a previously keptcopy of the second re-connection ticket. In another embodiment, thefirst protocol service 112 validates a first re-connection ticket forthe connection between the first protocol service 4502 and the hostservice 4516, or in another embodiment, between the first protocolservice 4502 and another first protocol service 4502 or an intermediarymachine 30. In a similar manner, each “hop” thereafter between the firstprotocol service 4502 and the host service 4516 may be validated withone or more tickets, either initial or re-connection tickets, tovalidate the continued use of the “hop” on behalf of the client machine10.

If the first protocol service 4502 determines the second re-connectionticket to be valid, the re-established first protocol connection 4504 bbetween the first intermediary machine 30 and the first protocol service4502 is linked to the maintained secondary protocol connection 4508between the first protocol service 4502 and each of the one or more hostservices 4516. Otherwise, if the first protocol service 4502 determinesthe second re-connection ticket to be invalid, the re-established firstprotocol connection 4504 b is not linked to the one or more maintainedsecondary protocol connections 4508 and the client machine 10 is refusedre-connection to the one or more host services 4516. In the case of amultiple-hop connection between the first protocol service 4502 and thehost service 4516, each “hop” may be validated for re-connection and belinked to the previous “hop” until the final “hop” to the host service4516 is validated, or until one of the “hops” is refused re-connection.

At step 7204, the second SID and key is deleted by, for example, thefirst protocol service 4502 and a replacement second SID and key isgenerated by, for example, the first protocol service 4502 fortransmission to the client machine 10. In such an embodiment, the firstprotocol service 4502 keeps a copy of the replacement second SID andkey. In some embodiments, the first protocol service 4502 waits for theclient machine 10 to acknowledge that it has received the replacementsecond SID and key before it proceeds to delete the second session IDand key

In some embodiments, the second re-connection ticket is deleted by, forexample, the first protocol service 4502 and a replacement secondre-connection ticket is generated by, for example, the first protocolservice 4502 for transmission to the client machine 10. In such anembodiment, the first protocol service 4502 keeps a copy of thereplacement second re-connection ticket. In some embodiments, the firstprotocol service 4502 waits for the client machine 10 to acknowledgethat it has received the replacement second re-connection ticket beforeit proceeds to delete the second re-connection ticket. In the case ofvalidating one or more of the “hops” for re-connecting a client 108, oneor more replacement re-connection tickets, at step 948, may be generatedand/or a copy saved by the ticket authority 136, intermediary nodes 632,any of the computing nodes, or one or more of the first protocolservices 112.

At step 7206, the replacement second SID and key are transmitted to theclient machine 10. For example, the ACR Service 5002 can transmit,through the intermediary machine 30, the replacement second SID and keyto the client machine 10. Moreover, in one embodiment, the firstprotocol service 4502 transmits, through the intermediary machine 30,the replacement second SID and key to the client machine 10.

In some embodiments, the replacement first re-connection ticket and thereplacement second re-connection ticket are transmitted to the clientmachine 10. For example, the ticket authority 6102 can transmit, throughthe intermediary machine 30, the replacement first re-connection ticketto the client machine 10. Moreover, in one embodiment, the firstprotocol service 4502 transmits, through the intermediary machine 30,the replacement second re-connection ticket to the client machine 10. Inother embodiments, the replacement re-connection tickets for one or more“hops” may be transmitted to one or more of the intermediary machine 30,any of the computing nodes, or one or more of the first protocolservices 4502.

Alternatively, in other embodiments, the methods described above providefor only a single re-connection ticket for the client machine 10 and/ora single re-connection for each of the “hops” between the client machine10 and a host service 4516. As such, rather than using both first andsecond re-connection tickets, in these embodiments, only theaforementioned single re-connection ticket is used. In one suchembodiment, the client agent 4506 of the client machine 10 is alsoprovided with the address of the first protocol service 4502. Tore-connect to the host services 4516, the client agent 4506 transmitsthe single re-connection ticket directly to the first protocol service4502. The first protocol service 4502 then determines whether the singlere-connection ticket is valid. In one embodiment, the first protocolservice 4502 determines the validity of the single re-connection ticketby comparing it to a previously kept copy of the single re-connectionticket. If the first protocol service 4502 determines the singlere-connection ticket to be valid, the re-established first protocolconnection 4504 between the client machine 10 and the first protocolservice 4502 is linked to the maintained secondary protocol connection4508 between the first protocol service 4502 and each of the one or morehost services 4516. Otherwise, if the first protocol service 4502determines the single re-connection ticket to be invalid, there-established first protocol connection 4504 is not linked to the oneor more maintained secondary protocol connections 4508 and the clientmachine 10 is refused re-connection to the one or more host services4516.

After the single re-connection ticket is validated, the singlere-connection ticket is deleted by, for example, the first protocolservice 4502 and a replacement single re-connection ticket is generatedby, for example, the first protocol service 4502 for transmission to theclient machine 10. In transmitting the replacement single re-connectionticket to the client machine 10, the first protocol service 4502 keeps acopy of the replacement single re-connection ticket. In someembodiments, the first protocol service 4502 waits for the clientmachine 10 to acknowledge that it has received the replacement singlere-connection ticket before it proceeds to delete the singlere-connection ticket.

In yet another embodiment, like the first and second re-connectiontickets, the single re-connection ticket is configured for automaticdeletion after a pre-determined period of time following a failure inthe connection 4504, and/or following a clean termination of theconnection 4504.

In an embodiment not shown in FIGS. 71-72, a ticket authority 6102 couldalso be used instead of the ACR Service 5002 for reconnecting a clientmachine 10 to a host service 4516. In the method 7100, the ticketauthority 6102 would generate and transmit reconnection tickets insteadof SIDs and keys as with the ACR Service 5002. For example, at step7106, a ticket authority 6102 would determine in step 7108 if a firstreconnect ticket received from the intermediary machine 30 in step 7106is valid. At step 7114 the ticket authority 6102 would delete the firstreconnection ticket and generates a second reconnection ticket with ahandle. As such, the ticket authority 6102 facilitates re-establishingand re-authenticating the communication session of the client machine 10to the host service 4516.

Performance of the network 150 can be monitored to increase performanceperceived by the user of a client machine 10. The bandwidth and latencyof the network 150 is a factor that affects the interaction experienceof the end-user of the client machine 10. Other factors include thenumber of virtual machines executing on a remote machine 30 or thenumber of applications executing within a virtual machine on the remotemachine 30, the amount of data being executed (or load) of theapplications, the amount of processing (or load) being done by theclient machine 10. During operation, each of these factors fluctuates.As data is transmitted through the network 150 the amount of availablebandwidth of the network is reduced. The number of requests to a remotemachine 30 increases and decrease thereby varying the load of the remotemachine 30. One aspect of the invention features systems and method fordetermining whether and how these independent changes affect theinteraction experience of the end-user.

FIG. 73 is a conceptual block diagram of an embodiment of a system thatincludes client software 7302 and remote machine software 7306 whichmonitor the status of the connection between the client machine 10 andthe remote machine 30. It should be understood the various modules arenot necessarily individual applications. Instead, the modules can beprovided as a single software application or grouped as any combinationof individual applications. Additionally, certain modules may bephysical hardware.

The client software 7302 is in communication with a transceiver module7304 of the client machine 10. The client software 7302 includes atrigger module 7308 in communication with the transceiver module 7304.The trigger module 7308 generates a message 7310 that is transmitted tothe remote machine software 7306. The message 7310 is configured togenerate a response from the remote machine software 7306 when themessage is processed by the remote machine 30. For example, the messagecan include a user input event that results in a graphical response fromthe remote machine. In one embodiment, the trigger module 7308 generatesthe message 7310 on a periodic basis. The length of the period can beconfigurable by the user of the client machine 10 or another user suchas a system administrator. In another embodiment, the trigger modulegenerates the message 7310 in response to a specific end-user inputusing input device 7312.

The transceiver module 7304 is in communication with network 150 and isconfigured to transmit the message 7310 from the client machine 10 tothe remote machine 30 via the network 150 and receive a response fromthe remote machine 30. If necessary, the transceiver module 7304 formatsthe message 7310 for transmission via the network 150 and formats theresponse for execution by the client software 7302.

Optionally, the client software 7302 can include a timer module 7316 anda calculation module 7314. The timer module 7316 is in communicationwith the trigger module 7308 and the calculation module 7314. The timermodule 7316 is configured to measure the elapsed time from thegeneration of the message 7310 until the client machine 10 completes theinstructions included in the response from the remote machine. In oneembodiment, the timer module 7316 generates a start timestamp and acompletion timestamp and determines the elapsed time therebetween. Inanother embodiment, the timer module acts as a stopwatch and generatesthe elapsed time without performing calculations. In one embodiment, theelapsed time is sent to another remote machine 30′ for furtherprocessing, such a calculation of an expected elapsed time, trendinganalysis, and storage. In another embodiment, the elapsed time isforwarded to the calculation module from comparison against an expectedvalue to determine if the environment 7300 is operating withinspecification. In still another embodiment, the elapsed time isforwarded to the remote machine 30 that the client is communicatingwith.

The remote machine software 7306 is in communication with a transceivermodule 7326 of the remote machine 30. The remote machine software 7306includes an echo application 7318, an optional initiation module 7320,and an optional confirmation module 7328. In one embodiment, the remotemachine software 7306 is in communication with the application programs7322 and the operating system 7324 that are executing on the remotemachine 30. In another embodiment, the remote machine software 7306 isin communication with a computing environment and a hypervisor executingon the remote machine 30. In still other embodiments, the remote machinesoftware 7306 executes in a virtual machine provided by a hypervisorand, in these embodiments, communicates with application programsprovided by the computing environment and the virtualized operatingsystem of the virtual machine. The echo application 7318 is incommunication with the transceiver module 7326 and if present each ofthe initiation module 7320 and the confirmation module 7328. In oneembodiment, the echo application 7318 is invisible to the end-user ofthe client machine 10. For example, the echo application 7318 can be awindowless (e.g., stealth application). The end-user does not interactdirectly with the echo application 7318.

The echo application generates a graphical response 7330 to the message7310 from the client software 7302. The graphical response message 7330includes instructions to manipulate, modify, update, alter, or changethe display of the client machine 10 in a manner that is not perceivableby the end-user of the client machine 10, but is perceivable by clientsoftware 7302 of the client machine 10. In one embodiment, the echoapplication 7318 executes invisibly alongside the application programs7322. In such an embodiment, the echo application 7318 is subject to thesame environmental effects and changes as the application programs 7322.

The transceiver module 7326 is in communication with network 150 and isconfigured to transmit the response 7330 from the remote machine 30 tothe client machine 10 via the network 150 and receive the message 7310from the client machine 10. If necessary, the transceiver module 7304formats the response 7330 for transmission via the network 150 andformats the message 7310 for execution by the remote machine 30. Thetransceiver module forwards the received message 7310 to the operatingsystem 7324 of the remote machine 30.

The operating system 7324 is configured to read and process the message7310 to generate an input event 7332 for the echo application 7318. Theinput event 7332 can be a known WINDOWS input event or a custom inputevent. Conceptually, the input event 7332 is configured to cause theecho application 7318 generate the graphic response 7330.

The initiation module 7320 is in communication with the applicationprograms 7322 and the operating system 7324. In one embodiment, theinitiation module 7320 monitors the application programs 7322 andautomatically initiates the echo application 7318 when a specific one ofthe application of the application programs 7322 begins executing on theremote machine 30. In another embodiment, the initiation module 7320initiates the echo application when the remote machine 30 receives themessage 7310. In another embodiment, the echo application 7318 isinitiated when a client/remote machine session begins and remainsquiescent until the message 7310 is received. It should be understoodthat the initiation module can initiate one or more instances of theecho application 7318. For example, the initiation module 7320 may starta respective echo application 7318 for each client machine 10 thatconnects to the remote machine 30 or that connects to a virtual machineprovided by the remote machine 30.

The confirmation module 7328 is in communication with the echoapplication 7318. In one embodiment, a function performed by theconfirmation module 7328 includes monitoring the echo application 7318to ensure an instance of the echo application 7318 is executing for eachconnection between a client machine 10 and a remote machine 30 that isof interest. The confirmation module 7328 may report whether the echoapplication 7318 is running and functioning properly to another remotemachine 30′, such as a management server described above, or theconfirmation module 7328 may report whether the echo application 7318 isrunning and functioning properly to the operating system 7324 of theremote machine 30 or to a virtual machine provided by a hypervisor.

With reference to FIG. 74, an embodiment of a method 7400 of operationand interaction between the client machine 10 and remote machine 30 isdescribed. As a general overview, the method can be conceptualized as agenerating a measurement for use in calculating an end-user experiencemetric in the remote machine based computing environment 7300. Theoperation of the client software 7302 and the remote machine software7306 includes transmitting the message 7310 to the application 7318(step 77410), receiving a graphic response (step 77420) from theapplication 7318, and determining an elapsed time (step 77430) thatrepresents the end-user's interaction experience.

In one embodiment, the trigger module 7308 on the client software 7302transmits the message 7310 via the transceiver 7304 on a periodic basis.In another embodiment, the trigger module 7308 generates the message7310 in response to end-user input. The message 7310 can includeinstructions to generate a WINDOWS message that is forwarded to theapplication 7318. Alternatively, the message 7310 can be the WINDOWSmessage and represent an input event to the application 7318. In oneembodiment, the message 7310 is transferred over a separate virtualchannel within the ICA protocol stream, and a WINDOWS message generatedby the remote machine software 7306 when the message 7310 is received.

When the remote machine software 7306 receives the message 7310, theecho application 7318 processes the instructions of the message 7310 andgenerates the graphic response 7330. In one embodiment, the graphicresponse 7330 generates a change on the display of the client that isundetectable by the end-user. In various embodiments, the graphicresponse 7330 can include instructions to change a small number ofpixels on the client display, instructions to change single pixel at theorigin (i.e., top left corner) of the client display, instructions tocycle a pixel of the display through a range of values, or instructionsto cycle a change through a range of pixel locations of the display.

When the client software 7302 processes the graphic response 7330, theelapsed time between the transmission of the transmission of the message7310 and the completion of the processing of the graphic response 7330is determined. In one embodiment, the client software 7302 determinesthe elapsed time and forwards the elapsed time to a management remotemachine 30′ for storage and trending analysis. In another embodiment, astart timestamp and an end timestamp are forwarded from the timer module7316 the management remote machine 30′. In such an embodiment themanagement remote machine 30′ determines the elapsed time. It should beunderstood that the elapsed time measurement is equivalent to theinteraction experience as used herein.

The management remote machine 30′ can store multiple interactionexperience measurements. The stored measurements can be used to isolatewhich portion of a client machine 10 connection is not performing asexpected. For example, network timing measurement for the same timeperiod can be compared to the interaction experience to isolateapplication, virtual machine, and execution machine load trends. Also,the stored interaction experience measurements can be analyzed usingknown methods to determine an expected interaction experience value. Theexpected value can be compared to the measured value, either by thecalculation module 7314 of the client software 7302 or the managementremote machine 30′.

With reference to FIG. 75, an embodiment of the operational method 7500of the remote machine 30 and remote machine software 7306 is described.After the client machine 10 initiates (step 77505) established a sessionwith a remote machine 30, the remote machine software initiates (step77510) the echo application 7318. The remote machine 30 receives (step77520) the message 7310 from the client machine 10. Once the message7310 is received, the confirmation module 7328 confirms (step 77530)that the echo application 7318 is executing. From the message 7310, theoperating system 7324, or the hypervisor, generates (step 77540) theinput event 7332 that is processed by the echo application to generate(step 77550) the graphic response 7330.

The remote machine software 7306 initiation module 7320 initiates (step77510) the echo application 7318 when the client machine 10 starts thesession. In one embodiment, a single echo application 7318 is initiated.In other embodiments, an echo application 7318 is started for each ofthe applications programs 7322 executing on the remote machine 30. Insuch embodiments, the interaction experience can be measured on anapplication by application basis. In other embodiments, an echoapplication 7318 is started for each of the virtual machines executingon the remote machine 30. In these embodiments, the interactionexperience can be measured on a virtual machine basis. In anotherembodiment, a single echo application 7318 is started for an executionmachine executing multiple program application programs 7322. Forexample, a remote machine may communicate with multiple client machines10. Each of the client machines 10 connects to the remote machine 30through a different network path and thus has a different interactionexperience. The echo application 7318 is not visible to the user. Thatis, the user does not interact directly with the echo application 7318and the echo application 7318 is not show on the display of the client.In one embodiment, the echo application 7318 is a windowlessapplication.

The transceiver module 7326 receives (step 77520) the message 7310 fromthe client machine 10. In one embodiment, the transceiver module 7326includes a network interface card that communicates with the network150. The transceiver module can format the received message 7310 so thatthe message 7310 is readable by the operating system 7324.

Prior to generating the graphic response 7330, the confirmation module7328 confirms (step 77530) that the echo application 7318 is executingin user space assigned by the operating system. In some embodiments, theuser space is assigned by the native operating system, that is, theoperating system of the execution machine. In other embodiments, theuser space is assigned by a virtualized operating system, that is, anoperating system of a virtual machine provided by a hypervisor. In oneembodiment, the confirmation module 7328 communicates an indication thatthe echo application 7318 is executing to the operating system. In oneembodiment, the remote machine 30 creates a log even on the remotemachine 30 to indicate that echo application 7318 was not running whenthe message 7310 was received or when the session was initiated.

Once confirmation of the execution of the echo application 7318 isreceived, the operating system processes the message 7310 therebygenerating (step 77540) the input event 7332. In one embodiment, theinput event is a WINDOWS message that is forwarded to the echoapplication 7318 to model a normal input event WINDOWS message. Theinput event is designed to cause the echo application 7318 to generate agraphic response 7330. Exemplary input events can include, but are notlimited to, mouse movements, keyboard strokes, window generation, windowdestruction, or any other event that generates a graphic response fromthe echo application 7318. In another embodiment, the input event is acustom “user-defined” application specific WINDOWS message.

The echo application 7318 processes the input event 7332 and generates(step 77550) the graphic response 7330, which is in turn forwarded tothe client machine 10. In various embodiments, the graphic response 7330is generated once the echo application 7318 has performed a set of taskssuch as: calculations, memory usage, disk access, and network resourceaccess. The echo application 7318 can be configured by an administratorto perform specified tasks. In another embodiment, the echo application7318 can perform execution tasks that mirror an application program 158executing on the remote machine 30 and generate the graphic response7330.

In one embodiment, the graphic response 7330 includes instructions thatcause a change on the display of the client machine 10 that is notdetectable by the end-user. For example, the graphic response 7330includes instructions to change a single pixel at the origin of thedisplay. More complex graphic responses can be used to differentiatefrom graphic generated by the application programs 7322 or to detect anyresponse indicators lost from graphic protocol optimizations. Forexample, the pixel value can cycle through an expected range of values.In another embodiment, the graphic response causes a pixel location tocycle through an expected range of pixel locations. Another example of agraphic response is a BitBlt with an unexpected Raster-Operation, eitherto the display or an off-screen surface (e.g., an off-screen buffer).

In addition to measuring the overall end-user interaction experience, invarious embodiments, sub-metrics that comprise the overall end-userinteraction experience metric can be measured and recorded. Generally,these sub-metrics include the time required by the client machine 10 togenerate and send the trigger message 7310, the network 150 latency, thetime required by the remote machine 30 to process the message 7310 andgenerate and transmit the graphic response 7330, and the time requiredby the client machine 10 to process the graphic response 7330.

With reference to FIG. 76 and FIG. 77, embodiments of a method ofgenerating client machine 10 sub-metrics are described. From theperspective of the client machine 10, there are two types of sub-metricsthat are generated a) those related to generating and transmitting thetrigger message 7310 as shown in FIG. 76 and b) those related todetecting and processing the graphic response 7330 as shown in FIG. 77.

With reference to FIG. 76, one embodiment of a method 7600 for capturingsub-metrics related to generating the trigger message 7310 is described.Assuming that the trigger message 7310 is generated in response to useof the input device 7312, the trigger module 7304 detects (step 77610)use of the input event and marks (step 77620) the time of detection. Thetrigger module generates (step 77630) the message 7310 and marks (step77640) the time the message generating is completed. The trigger module7308 forwards the message 7310 to the transceiver 304, which thentransmits (step 77650) the message 7310 to the remote machine 30. Thetrigger module 7308 or the transceiver module 7304 marks (step 77660)the time the message 7310 is transmitted to the remote machine 30.

With reference to FIG. 77, one embodiment of a method 7700 for capturingsub-metrics related to processing the response 7330 is described. Thetransceiver 304 receives (step 7710) the graphic response 7330 from theremote machine 30 and marks (step 7720) the time of receipt. The clientsoftware 7302 process (step 7730) the graphic response 7330. Uponcompletion of processing the graphic response 7330, the client software7302 marks (step 7740) the time of completion. Once complete, the clientsoftware 7302 displays the graphic response and detects (step 7750) thatthe graphic response 7330 is displayed. The client software 7302 alsomarks (step 7760) the time of detection on the display.

The above-described actions of marking certain times that indicate theoccurrence of certain events can occur in different ways. In oneembodiment, multiple timers are started and stopped by the timer module7316 upon the occurrence of each of the above-described events. Inanother embodiment, a single timer is used and the split times (i.e.,the time elapsed between the occurrence of the events) are saved in atable that is accessible by the calculation module 7314. In stillanother embodiment, a time stamp is added to the message 7310 and thegraphic response 7330 for each of the marking actions. In such anembodiment, prior to transmitting the message 7310 the time stamps arereported to the calculation module 7314, where the elapsed time betweeneach time stamp is determined. These elapsed times represent theabove-described different sub-metrics. It should be understood thatvarious combinations of the elapsed times can also be used. For example,the time stamp related to the detection of the use of the input deviceand the time stamp that indicates the transmission of the message 7310can be processed to determine the total elapsed used by the clientmachine 10 to generate and send the message 7310 to the remote machine30. The principles described above with respect to the generation of themessage 7310 are equally applicable to the processing of the graphicresponse 7330 by the client machine 10.

With reference to FIG. 78, one embodiment of a method 7800 for capturingsub-metrics related to generating the graphic response 7330 isdescribed. The transceiver 320 receives (step 7810) the message 7310from the client machine 10 and marks (step 7820) the time of receipt.The operating system 7324 then generates (step 7830) the input event7332. The remote machine software 7306 marks (step 7840) the time ofcompletion of the generation of the input event 7332. The echoapplication 7318 receives (step 7850) the input event 7332 and theremote machine software 7306 marks (step 7860) the time of receipt ofthe input event 7332. Once the echo application 7318 receives the inputevent, the echo application 7318 generates (step 7870) the graphicresponse 7330. The remote machine software 7306 marks (step 7880) thetime the echo application 7318 completes generating the graphic response7330. In one embodiment, the time required to generate the graphicresponse 7330 by the echo application 7318 includes the echo applicationperforming additional executions tasks that similar to those performedby the application programs 7322. The transceiver module 7326 receivesthe graphic response 7330 and transmits (step 7890) the graphic response7330 to the client machine 10. The remote machine software also marks(steps 900) the time the graphic response 7330 is sent.

Similar to the marking of events described with reference to the clientmachine 10, the same methods can be employed with regard to the remotemachine 30. In one embodiment, multiple timers are started and stoppedby the timer module 7316 upon the occurrence of each of theabove-described events. In another embodiment, a single timer is usedand the split times (i.e., the time elapsed between the occurrence ofthe events) are saved in a table that is accessible by the calculationmodule 7314. In still another embodiment, a time stamp is added to thegraphic response 7330 for each of the marking actions. In such anembodiment, upon receipt of the graphic response 7330 the time stampsare reported to the calculation module 7314, where the elapsed timebetween each time stamp is determined. These elapsed times represent theabove-described different sub-metrics. It should be understood thatvarious combinations of the elapsed times can also be used. For example,the time stamp related to detecting receipt of the message 7310 and thetime stamp that indicates the transmission of the graphic response 7330can be processed to determine the total elapsed used by the remotemachine 30 to generate and send the graphic response to the clientmachine 10.

Referring now to FIG. 79, another system for increasing the convenienceand usability of the systems described above is shown. A client-servercomputer system 7900 includes a first client machine 10, a second clientmachine 10, and a remote machine 30. The depiction of two clientmachines is for illustrative purposes only. The client-server computersystem can include any number of client machines.

In one embodiment, the first client machine 10 includes an input module7908, a client process 7910, a network module 7912, and a display module7914. The input module 7908 provides an interface for a user of thefirst client machine 10 to interact with the first client machine 10,for example to request the remote execution of an application 7916 in anapplication session 7918 from the remote machine 30.

An application session 7918 is a process, operating on the remotemachine 30 that provides access to or supports the execution of one ormore resources, such as application 7916. An application 7916 can be asoftware program, for example, or any organized set of software codecapable of being executed by a computer, or hardwired into circuitry inthe form of an Application Specific Integrated Circuit (ASIC), read onlymemory (ROM) microchip, and the like. Example applications include, butare not limited to Microsoft Word (available from Microsoft CorporationRedmond, Wash.), Internet Explorer (Microsoft), Acrobat (available fromAdobe Systems, Inc. San Jose, Calif.), etc. In one embodiment, anapplication session 7918 includes a desktop application 7916 from whichthe execution of other application 7916 can be initiated. Applicationsessions 7918 can be nested within other application sessions 7918. Inanother embodiment, the application session 7918 includes an instance ofthe execution of a single application 7916.

In one embodiment, the input module 7908 is, for example, a graphicaluser interface that provides one or more icons or menu selections for auser to select. Each icon or menu selection represents a specificapplication 7916 available for remote execution. Selecting an icon ormenu selection initiates the transmittal of a log-on request to theremote machine 30 for access to that application 7916. In anotherembodiment, an icon or menu selection does not represent any specificapplication 7916, but instead represents a general remote machine 30log-on procedure. In another embodiment, the input module 7908 isnon-graphical user interface. In this embodiment, the user can enter acommand to send a log-on request to remote machine 30. Entering acommand can include typing a predefined set of characters or depressinga specified key sequence on an input device (e.g., a keyboard orkeypad). The log-on request at least includes user-providedauthentication information. The input module 7908 accepts the input ofthe user-provided authentication information, which can include any typeof authentication information, including without limitation any of username-password/PIN combinations, voice samples, one-time passcodes,biometric data, digital certificates, smart card data, etc. In someembodiments, the input module 7908 is in communication with additionalhardware peripherals (not shown) to facilitate acceptance of userauthentication information. In other embodiments, the input module 7908can accept authentication information outside of the log-on process.

The input module 7908 accepts authentication information and provides itto the client process 7910. The client process 7910 then manages theclient side functionality of the remotely executing application session.The client process 7910 forwards user input including the authenticationinformation and requests for termination or disconnection of applicationsessions 7918 to the remote machine 30. The client process 7910 alsohandles data incoming from the remote machine 30, for example, byforwarding the graphical output of an application session 7918 to thedisplay module 7914.

The network module 7912 provides for communication between the firstclient machine 10 and the remote machine 30. The network module sendsuser input, such as authentication information and requests for accessto, disconnection from, or termination of application sessions 7918executing on the remote machine 30. The network module also receivesoutput from the application sessions 7918 and forwards the output to theclient process 7910. In one embodiment, the network module 7912encapsulates user input into, and reconstitutes application sessionoutput from, a predetermined protocol for transmission to the remotemachine 30. In another embodiment, the network module encrypts outgoingtransmissions and decrypts incoming transmissions.

The display module 7914 displays the output of an application 7916 froma remotely-executing application session 7918. The network module 7920provides communication functionality for the remote machine 30. Forexample, the network module 7920 receives communications from first andsecond client machines 10 over one or more data networks or links 150.The network module 7920 also transmits resource output data to the firstand second client machines 10. In one embodiment, the network module7920 encrypts outgoing communications and decrypts incomingcommunications. Likewise, in one embodiment, the network module 7920encapsulates outgoing communications in a protocol for transmission andretrieves incoming data from transmissions received according to aprotocol. Protocols can include, for example and without limitation,HTTP, Independent Computing Architecture (ICA) protocol (used by Citrix,Systems, Inc. Ft. Lauderdale, Fla.), Remote Desktop Protocol (RDP)(Microsoft Corporation), or Common Gateway Protocol (CGP) (Citrix). Thenetwork module 7920 of the remote machine 30 communicates with thenetwork module 7912 of the first client machine 10 over a network 150.The network 150 can be implemented with any of a variety of suitabletechnologies. Incoming communications, once decrypted or retrieved froma protocol (if necessary), are forwarded to an application session 7918or to the server process 7922, as appropriate.

The server process 7922 manages the execution, suspension to disk,resumption of execution, suspension without writing state to disk, andtermination of application sessions 7918 and the connections anddisconnections of those application sessions 7918 to the first andsecond client machines 10 . The server process 7922 can initiate newapplication sessions 7918, disconnect a client machine 10 from anapplication session 7918, detect a client machine 10 disconnection froman application session 7918, locate an application session 7918 fromwhich a user has disconnected, locate an application to which a user ofthe first client machine 10 is connected to from the second clientmachine 10, and connect a user to a disconnected application session7918. In some embodiments, the application sessions 7918 are provided soas to be configured with the user's personal preferences and accessallowances.

The server process 7922 may execute in the hypervisor, a virtual machineprovided by the hypervisor, a guest operating system executing in avirtual machine, an operating system provided by the physical machine orin combinations of those entities.

The application output transmitter 7924 transmits output from anapplication session 7918 to a client machine 10 through the networkmodule 7920. The application output transmitter 7924 intercepts theoutput of an application session 7918 and determines which clientmachine 10 is connected to the application session 7918. In otherembodiments, the identity of the client machine 10 that is connected tothe application session 7918 is stored at the time the connection ismade. If the application session 7918 is connected to a client station,the application output transmitter 7924 transmits the application outputdata to the connected client machine 10 via the network module 7920. Inone embodiment, if the application session is not connected to a clientmachine 10, the application output transmitter 7924 discards theapplication output data and waits to receive future application outputdata. In another embodiment, if the application session 7918 is notconnected to a client machine 10, the application output transmitter7924 disregards all further application output data until theapplication output transmitter 7924 receives notification that theapplication session 7918 has connected to a client machine 10. Inanother embodiment, the application output transmitter 7924 stores thedata until the application output transmitter 7924 receives notificationthat the application session 7918 has connected to a client machine 10.In another embodiment, the application output transmitter 7924 attemptsto send application output data to a client machine 10 until the serverprocess 7922 notifies the application output transmitter 7924 that theclient machine 10 is disconnected from the remote machine 30. In oneembodiment, the application output transmitter 7924 determines whichclient machine 10, if any, the application session 7918 is connected toby consulting the data store 7926.

The data store 7926 includes information related to application sessionsinitiated by users. The data store can be stored in volatile ornon-volatile memory or, for example, distributed through multipleservers. In some embodiments, the functionality of a data store 7926 isprovided by a session server 8620 as described in connection with FIG.86.

In one embodiment, remote machine 30 also includes a rules source 7928.The rules source 7928 stores rules governing the reaction of the serverprocess 7922 to a user transmitting authentication information to theremote machine 30. In one embodiment, the rules stored in the rulessource 7928 are specified at least in part by the system administrator.In another embodiment, a user specifies at least some of the rulesstored in the rules source 7928. The user-specified rule(s) are storedas preferences. The rules source 7928 can be stored in volatile ornon-volatile memory or, for example, distributed through multipleservers.

One rule stored in the rule source 7928, for example, might require orforbid automatic connection to disconnected application sessions 7918.Another rule might require or forbid automatic connection to activeapplication sessions 7918 currently connected to a different clientmachine 10. Yet another rule might make connection and/or connectioncontingent on the client machine 10 that requests access being within asecure network. A further rule might only allow connection toapplication sessions 7918 after receiving user approval. Another rulemight only allow connection for a predetermined time afterdisconnection. Still another rule only allows connection to applicationsessions 7918 that include specific application 7916.

The authentication module 7930 is responsible for authenticating a userthat attempts to log on to the remote machine 30. The authenticationmodule 7930 receives user-provided authentication informationtransmitted from the first client machine 10. The authentication module7930 then authenticates the user based on the user-providedauthentication information. In response to a successful authentication,the authentication module 7930 transmits the results of theauthentication process (e.g., allow or deny access, the user's systemID, client computer ID, user access permissions, etc.) to the serverprocess 7922.

In one embodiment, the above-described modules and processes of theremote machine 30 (i.e., the network module 7920, the server process7922, the application output transmitter 7924, and the authenticationmodule 7930) and a client machine 10 (i.e. the input module 7908, theclient process 7910, the network module 7912 and the display module7914) are all implemented in software executable on one of severalcomputer operating systems, including without limitation the Windowsfamily of operating systems (Microsoft Corporation), the MacOS family ofoperating systems (Apple Computer, Inc., Cupertino, Calif.), and Unixbased operating systems (e.g., Solaris, Sun Microsystems, Sunnyvale,Calif.). In other embodiments, one or more modules or processes areimplemented in hardware as application specific integrated circuits(ASICs), Read Only Memory (ROM) devices, or other digital hardwarecircuitry.

Unintentional termination of application sessions 7918 resulting fromimperfect network connections and users' failure to terminate theirapplication sessions 7918 themselves can lead to user difficulties. Oneembodiment of the invention limits these difficulties by differentiatingdisconnection (which is treated as if the user is not done working withan application session 7918) from termination (which is assumed to be anintentional end to the application session) and by correlatingapplication sessions 7918 with users as opposed to client machines. Whena user is finished using an application 7916 operating in an applicationsession 7918, the user can terminate an application session 7918.Termination generally involves the affirmative input of the userindicating that the server should no longer maintain the applicationsession 7918. Such affirmative user input can include selecting an“Exit” option from a menu, clicking on an icon, etc. In response to theserver process 7922 receiving a termination request, the execution ofthe application session 7918 and any application 7916 within thatapplication session 7918 is halted. In one embodiment, data related tothe application session 7918 is also removed from the data store 7926.

Disconnection, either intentional or unintentional, on the other hand,does not result in termination of application sessions 7918. Since theapplication or applications operating in an application session 7918 areexecuting on the remote machine 30, a connection to the first clientmachine 10 is not usually necessary to continue execution of theapplication 7916, and in one embodiment the application 7916 cancontinue to execute while waiting for the user to connect. In analternative embodiment, upon disconnection of a user, the server process7922 stalls the execution of the application 7916 operating in theapplication session 7918. That is, the server process 7922 halts furtherexecution of the application 7916, and the server process 7922 storesthe operational state of the application 7916 and any data theapplication 7916 is processing. In a further embodiment, the serverprocess 7922 can selectively stall execution of specific application7916 after a user disconnects. For example, in one embodiment, theserver continues execution of an application 7916 for a fixed timeperiod, and if a user fails to connect within that time period, theserver process 7922 stalls the application 7916. In another embodiment,the server stalls specified application sessions 7918 that cannotcontinue executing without user input. In each of the above-describedembodiments, if the user of the first client machine 10 disconnects fromthe remote machine 30 and then connects to the remote machine 30 whileoperating the first client machine 10, the second client machine 10, ora third client computer, the server process 7922 can connect the clientcomputer operated by the user to one or more previously initiated,non-terminated application session(s) 118 associated with the user, andreinitiate execution of any stalled application 7916.

In one embodiment, the server process 7922 detects a disconnection. Auser can intentionally and manually instruct the server to disconnect anapplication session 7918 from the client machine 10 that the user iscommunicating from. For example, in one embodiment, application sessions7918 provide a menu option for disconnection (as distinguished fromtermination above) that a user can select. The server process 7922 canalso detect an unintentional disconnection. For example, in oneembodiment, the network module 7920 of the remote machine 30 informs theserver process 7922 when a predetermined number of data packetstransmitted by the network module 7920 to a client machine 10 have notbeen acknowledged by the client machine 10. In another embodiment, theclient machine 10 periodically transmits a signal to the remote machine30 to confirm that a connection is still intact. If the server process7922 detects that a predetermined number of expected confirmationsignals from a client machine 10 have not arrived, the server process7922 determines that the client machine 10 has disconnected. If theserver process 7922 detects that a user has disconnected from anapplication session 7918, either intentionally, or unintentionally, theentry in the data store 7926 related to the disconnected applicationsession 7918 is modified to reflect the disconnection. Referring also toFIG. 80, a method 8000 of providing remote access to an applicationsession, in one embodiment, begins with the network module 7920 of theremote machine 30 receiving authentication information associated with auser (step 8002). Authentication information can include a number oftypes of authentication information, including without limitation usernames, client names, client addresses, passwords, PINs, voice samples,one-time passcodes, biometric data, digital certificates, tickets, etc.and combinations thereof. The authentication information could be in theform of a log-on request from a user. As described above, a log-onrequest can be initiated by a user through the input module 7908 of aclient machine 10. The client's network module forwards the request tothe server process 7922.

In one embodiment, upon receiving the request, the server process 7922forwards the user-provided authentication information to theauthentication module 7930, which authenticates the identity of theuser. The server's authentication module 7930 can perform theauthentication itself and/or in cooperation with one or other modules orcomputers, such as a domain server, an authentication service, etc.Successful authentication results in the authentication moduletransmitting identification information for the user (e.g., a usernameor ID) to the server process 7922.

In response to receiving authentication information associated with theuser the server process 7922 identifies any disconnected applicationsessions 7918 associated with the user that are executing, stalled onthe remote machine 30, or suspended to disk (step 8004). In oneembodiment, the server process 7922 identifies the application sessions7918 upon receiving the authentication information. In anotherembodiment, the server process identifies the applications in responseto receiving the authentication information after the authenticationmodule 7930 verifies of the user's identity. In one embodiment, serverprocess 7922 determines whether any such disconnected applicationsessions 7918 exist by consulting the data store 7926 for sessions,which is some embodiments is a persistent data store, related to theuser. For example, the disconnected application session 7918 could havebeen disconnected by direction of the user of the application session7918, resulting in the server process 7922 disconnecting the applicationsession 7918, for example, by modifying the status of applicationsession 7918 in the data store 7926 to “disconnected,” and deleting theidentification of the connected client machine 10 in the data store 7926entry for the application session 7918. In another embodiment, thedisconnection was unintentional. Unintentional disconnection results inthe server process 7922 making the same modifications to the data store7926 as would be made as a result of an intentional disconnection.

Upon identifying any disconnected application sessions 7918 (step 8004),in one embodiment, the server process 7922 prompts the user to indicatewhether connection is desired. If connection is not desired, the serverprocess 7922 prompts the user to indicate whether the disconnectedapplications sessions 7918 should remain disconnected, or whether theapplication sessions 7918 should be suspended to disk, paused, orterminated. In an alternative embodiment, the server process 7922consults a rule stored in the rules source 7928 to determine whetherconnection and/or connection is permitted and/or required.

In an alternative embodiment, the user connects to the remote machine30, the server process 7922, and any disconnected application sessionsby utilizing a single user interface element, for example clicking anicon labeled “Log-on.” In this embodiment, activating the single userinterface will automatically connect the user to any disconnectedapplications sessions 7918.

In one embodiment, the client can be configured to automatically sendauthentication information upon such user connection. If connection ispermitted, and is either assented to by user or is automatic, the serverprocess 7922 connects the user to the disconnected application sessions(step 8006). In one embodiment, connection includes modifying the entryin the data store 7926 to indicate that the user is connected to theapplication session 7918 and to indicate from which client machine 10the user is connected to the server. Upon connection, the remote machine30 resumes transmitting application output data from the applicationoutput transmitter 7924 to the client 10 (step 8008). In anotherembodiment, the application output transmitter consults the rules source7928 before beginning transmitting application output to ensure suchtransmission is permitted.

Application sessions are associated primarily with users instead of theclient machine 10 which the user was operating when the user previouslyhad connected to, (and then been disconnected from) the server. As aresult, rules permitting, the user can reconnect to an applicationsession 7918 from the first client machine 10, the second client machine10, or any other client computer. In other embodiments, the user of theclient machine 10 may be given further options, such as “reconnect toall sessions not executing on a virtual machine,” suspend all sessionsexecuting on a virtual machine,” “reconnect all sessions currentlyhosted,” or “reconnect to all session not suspended,” for example.

Referring to FIG. 81, even if a session is not disconnected (i.e., isactive) it can be useful to transfer the session from one client toanother. For example, it may be that an application session wasdisconnected, but the server did not yet detect the disconnection. Itmay be that the user deliberately left a session running, but would nowlike to access the session from another location.

A method 8100 for transferring active application sessions 7918 from afirst client machine 10 to a second client machine 10 typically beginswith the network module 7920 receiving authentication information from auser, for example in the form of a log-on request. In one embodiment,the user submits the authentication information via the input module7908. The authentication information can be transmitted by the networkmodule 7912 of second client machine 10 to the remote machine 30. Thenetwork module 7920 of the remote machine 30 can forward the request tothe server process 7922.

The server process 7922 receives the user-provided authenticationinformation (step 8102). In one embodiment, the server process 7922forwards the user-provided authentication information to anauthentication module 7930, which authenticates the identity of the userusing, for example, any of the variety of authentication techniquesdescribed above. Successful authentication results in the authenticationmodule transmitting for example, identification information for the userto the server process 7922.

After receiving authentication information (step 8102), the serverprocess consults the data store 7926 to identify any active applicationsessions 7918 that are associated with the user, but that are connectedto a different client computer, such as the first client machine 10 asan illustrative example (step 8104). In one embodiment, if the serverprocess 7922 identifies any such active application sessions 7918, theserver process automatically disconnects the application session(s) 118from the first client machine 10 (step 8106) and connects theapplication session(s) 118 to the current client machine 10 (step 8108).In one embodiment, the user can trigger the automatic consultation ofthe data store and subsequent connection with the selection of a singleuser interface element.

In an alternative embodiment, the server process 7922 prompts the useras to whether the user wants to have the active application session(s)118 connected to the current client machine 10. If the user declines totransfer one or more of the active application session(s), the serverprocess 7922 prompts the user to either keep the application session(s)118 active, suspend the application session to disk, pause theapplication session, or to terminate the application session(s) 118. Inan alternative embodiment, the server process 7922 consults a rulestored in the rules source 7928 to determine whether transfer of theactive application session(s) 118 are permitted before transferring theactive application session(s) 118.

If transfer of the application session(s) 118 are permitted and transferis automatic or requested by the user, in one embodiment the serverprocess 7922 carries out the disconnection (step 8106) and connection(step 8108) by modifying the entry maintained in the data store 7926 forthe application session 7918 to substitute the identity of the storedclient machine 10 with the identity of the current client computer, i.e.the client machine 10. Upon connection with the current client machine10, the application output transmitter 7924 begins transmittingapplication output to the current computer (step 8110). In anotherembodiment, the application output transmitter consults the rules source7928 before beginning transmitting application output to ensure suchtransmission is permitted.

It should be understood that the methods of FIG. 80 and FIG. 81 can becombined to allow a client to be connected to disconnected, suspended,paused, and active sessions associated with a user. In addition, priorto transfer or reconnection, the active and/or disconnected sessionscould have been connected to the same or several different clientmachines.

Referring to FIG. 82, as mentioned above, the remote machine 30 can beimplemented as a machine farm 38. In one embodiment, the machine farm 38includes several remote machines 30, 30′, and 30″, which are linkedtogether and which are jointly administered. Several client machines 10,10′, and 10″ (typically many computers) can connect to the machine farm38 over a network 150. The servers 30, 30′, and 30″ share thecomputational load put on the machine farm 38. For example, if a user isaccessing three application sessions 8218 a, 8218 b, and 8218 c, eachapplication session can be executing on a different server 30, 30′, or30″. Similarly, if the user is accessing two or more application 7916through a single application session 8218 a, 8218 b or 8218 c, theserver process 7922 of the machine farm 38 can assign one application toexecute on one server 30 and another application to execute on server30′. In a machine farm configuration, the modules of the server 120,122, and 124, the data store 7926, and the rules source 7928 (FIG. 1),can be stored on a single server 30, 30′ or 30″, or can be distributedamong the servers 30, 30′, and 30″.

With respect to connecting to the machine farm 38 after a disconnectionor after changing client machines 10, 10′ and 10″ without disconnecting,the server process 7922 treats the servers 30, 30′, and 30″ as a singleserver. That is, if a machine farm is executing a user's applicationsessions 8218 a, 8218 b, and 8218 c on separate servers 30, 30′, and30″, and the user disconnects from the machine farm 38 or changes theclient computer 10, 10′, or 10″ at which the user is working, uponsubsequently connecting to the machine farm 38, the server process 7922of the machine farm 38 can automatically connect the user's clientcomputer 10, 10′, or 10″ with all three application sessions 8218 a,8218 b, and 8218 c executing on all three severs 30, 30′, and 30″.

In one embodiment of the system, a user of a first client computer 10,which in this example is a mobile handheld computer, logs on to themachine farm 38 via a wireless modem and requests two applicationsessions 8218 a and 8218 b. The server process 7922 of the machine farm38 launches a first application session 8218 a on a first server 30 anda second application session on a second server 30′. The wireless modemloses its connection with the machine farm when the user of the firstcomputer 10 enters an elevator. The server process 7922 of the machinefarm 38 determines that the user is disconnected, and the server process7922 updates the data store 7926 accordingly.

The user then logs on to the machine farm 38 from a second clientcomputer 10′, which in this example is a desktop computer in his office.The server process 7922 consults the data store 7926 and determines thattwo disconnected application sessions 8218 a and 8218 b are associatedwith the user. The server process 7922 (assuming no rules to thecontrary) automatically connects the second client computer 10′ to bothapplication sessions 8218 a and 8218 b executing on servers 30 and 30′,respectively.

The user then leaves the second client computer 10′ withoutdisconnecting from the machine farm 38 and logs on to the machine farm38 from a third client computer 10″, for example a colleague's laptop.Upon logging on from the third client computer 10″, the server processconsults the data store 7926 and determines that the user is associatedwith the two active application sessions 8218 a and 8218 b connected tothe second client computer 10′. The server process 7922 (assuming norules to the contrary) then automatically disconnects both of theapplication sessions 8218 a and 8218 b from the second client computer10′, and connects both of the application sessions 8218 a and 8218 b tothe third client computer 10″.

The user next selects a disconnect option for each application session8218 a and 8218 b. The server process 7922 updates the data store 7926to indicate that the application sessions 8218 a and 8218 b have beendisconnected. The user then logs on to the machine farm 38 from thesecond client computer 10′. The server process 7922 consults the datastore 7926 and determines that two disconnected application sessions8218 a and 8218 b are associated with the user. The server process 7922(assuming no rules to the contrary) automatically connects thedisconnected application sessions 8218 a and 8218 b to the second clientcomputer 10′.

Referring now to FIG. 83, a flow diagram depicts one embodiment of thesteps taken in a method for providing remote access to a computingenvironment provided by a virtualized operating system. In briefoverview, authentication information associated with a user of a clientmachine 10 is received (step 8302). Based on the received authenticationinformation, a computing environment provided by a virtualized operatingsystem and already associated with the user is identified (step 8304). Aconnection is established between the client machine 10 and theidentified computing environment (step 8306).

In some embodiments the methods and systems described above inconnection with FIGS. 79-82 may be implemented in systems includingvirtual machines. In some embodiments, the client machine 10 hasestablished a connection to a physical machine providing access to aresource requested by the client machine 10. In this embodiment, theclient machine 10 may be connected to a disconnected application sessionand receive application output as described above in connection withFIGS. 79-82.

In other embodiments, the client machine 10 has established a connectionto a virtual machine providing access to a resource. In one of theseembodiments, the client machine 10 may be reconnected to an applicationsession executing on the virtual machine. In another of theseembodiments, the client machine 10 may be reconnected to a plurality ofapplication sessions executing within a computing environment providedby a virtual machine. In still another of these embodiments, the clientmachine 10 may be reconnected to an application session comprising aplurality of application programs executing within a computingenvironment provided by a virtual machine. In yet another of theseembodiments, the client machine 10 may be reconnected to an applicationsession comprising a plurality of computing environments provided by avirtual machine.

Referring still to FIG. 83, and in greater detail, authenticationinformation associated with a user of a client machine 10 is received(step 8302). In one embodiment, responsive to the receivedauthentication information, a collection agent gathers information aboutthe client machine 10. In some embodiments, the user of the clientmachine 10 is authenticated responsive to the received authenticationinformation.

Based on the received authentication information, a computingenvironment provided by a virtualized operating system and alreadyassociated with the user is identified (step 8304). In some embodiments,the authentication information includes an access control decision,generated as described above in connection with FIGS. 7A and 7B. Asdescribed above, a client machine 10 requests access to a resource, acollection agent gathers information about the client machine 10, and apolicy engine makes an access control decision. In one of theseembodiments, the identification of the computing environment alreadyassociated with the user is made in response to the receivedauthentication information. In another of these embodiments, aconnection is established between the client machine 10 and theidentified computing environment. In still another of these embodiments,a remote machine 30, acting as an intermediary server, receives theauthentication information including the access control decision, andestablishes a connection between the client machine 10 and a remotemachine 30′, acting as an execution machine providing the user of theclient machine 10 with access to the requested resource.

In one embodiment, based on the received authentication information andgathered client machine information, a computing environment provided bya virtualized operating system and already associated with the user isidentified. In another embodiment, stored data associated with at leastone computing environment is consulted to identify, based on thereceived authentication information, a computing environment provided bya virtualized operating system and already associated with the user. Instill another embodiment, based on the received authenticationinformation, an identification is made of a first computing environmentprovided by a first virtualized operating system and a second computingenvironment provided by a second virtualized operating system, the firstand second computing environments already associated with the user. Inyet another embodiment, based on the received authenticationinformation, an identification is made of a first computing environmentprovided by a first virtualized operating system executing on a firstserver and a second computing environment provided by a secondvirtualized operating system executing on a second server, the first andsecond computing environments already associated with the user

A connection is established between the client machine 10 and theidentified computing environment (step 8306). In one embodiment, theconnection is established between the client machine 10 and theidentified computing environment subject to a rule. In anotherembodiment, a connection is established between the client machine 10and the identified computing environment subject to a policy applied tothe received authentication information and gathered client machineinformation.

In some embodiments, a request is received to disconnect the clientmachine from the identified computing environment. In one of theseembodiments, the connection between the client machine and theidentified computing environment is terminated. In another of theseembodiments, a data record associated with the identified computingenvironment is updated to indicate that the client machine isdisconnected. In still another of these embodiments, an execution of theidentified computing environment is continued. The execution maycontinue although the client is disconnected from the identifiedcomputing environment.

In some embodiments, authentication information associated with the useris received. In one of these embodiments, the user uses a second clientmachine 10′. In another of these embodiments, an identification is made,based on the received authentication information of a computingenvironment provided by a virtualized operating system and alreadyassociated with the user. In still another of these embodiments, aconnection is established between the second client machine 10′ and theidentified computing environment. In yet another of these embodiments,the connection between the first client machine 10 and the identifiedcomputing environment is terminated.

Referring now to FIG. 84, a flow diagram depicts an embodiment of thesteps taken in a method for providing remote access to a plurality ofapplication sessions. In brief overview, a selection of a single userinterface element by a user of a client machine 10 is received at theclient machine 10 (step 8410). In response to the user interface elementselection, authentication information associated with the user istransmitted (step 8412). Based on the transmitted authenticationinformation, a computing environment provided by a virtualized operatingsystem and already associated with the user is identified (step 8414). Aconnection is established between the client machine and the identifiedcomputing environment (step 8416).

A selection of a single user interface element by a user of a clientmachine 10 is received at the client machine 10 (step 8410). In responseto the user interface element selection, authentication informationassociated with the user is transmitted (step 8412). In one embodiment,a collection agent gathers information about the client machine inresponse to the received information. In another embodiment, a policyengine makes an access control decision responsive to the gatheredinformation, as described above in connection with FIG. 7A and FIG. 7B.In some embodiments, based on the received authentication informationand on gathered client machine information, an identification is made ofa computing environment provided by a virtualized operating system andalready associated with the user. In other embodiments, the user isauthenticated responsive to the received authentication information.

Based on the transmitted authentication information, a computingenvironment provided by a virtualized operating system and alreadyassociated with the user is identified (step 8414). In one embodiment, aconnection is established between the client machine and the identifiedcomputing environment subject to a rule applied to the receivedauthentication information and to gathered client machine information.In another embodiment, based on the received identification, anidentification is made of a first computing environment provided by afirst virtualized operating system and a second computing environmentprovided by a second virtualized operating system, the first and secondcomputing environments already associated with the user. In stillanother embodiment, based on the received authentication information, anidentification is made of a first computing environment provided by afirst virtualized operating system executing on a first server and asecond computing environment provided by a second virtualized operatingsystem executing on a second server, the first and second computingenvironments already associated with the user. In some embodiments,stored data associated with at least one computing environment isconsulted to identify, based on the received authentication information,a computing environment provided by a virtualized operating system andalready associated with the user.

A connection is established between the client machine and theidentified computing environment (step 8416). In one embodiment, theconnection between the client machine and the identified computingenvironment is made subject to a rule. In some embodiments,authentication information associated with the client machine 10 isreceived including an access control decision, generated as describedabove in connection with FIGS. 7A and 7B. In one of these embodiments,the identification of the computing environment already associated withthe user is made in response to the received authentication information.In another of these embodiments, a remote machine 30, acting as anintermediary broker server, receives the authentication informationincluding the access control decision, and establishes a connectionbetween the client machine 10 and a remote machine 30′, acting as anexecution machine providing the user of the client machine 10 withaccess to the requested resource.

In some embodiments, a request is received to disconnect the clientmachine from the identified computing environment. In one of theseembodiments, the connection between the client machine and theidentified computing environment is terminated. In another of theseembodiments, a data record associated with the identified computingenvironment is updated to indicate that the client machine isdisconnected. In still another of these embodiments, execution of theidentified computing environment is continued. The execution maycontinue although the user has terminated the connection between theclient machine and the identified computing environment.

In some embodiments, authentication information associated with the useris received, the user using a second client machine 10′. In one of theseembodiments, based on the received authentication information, anidentification is made of a computing environment provided by avirtualized operating system and already associated with the user. Inanother of these embodiments, a connection is established between thesecond client machine 10′ and the identified computing environment. Inyet another of these embodiments, a connection between the first clientmachine 10 and the identified computing environment is terminated.

Referring now to FIG. 85, a block diagram depicts one embodiment of aserver for providing remote access to a computing environment. In briefoverview, a remote machine 30 is a server and includes a network module7920, a data store 7926, and a broker process 8532. In some embodiments,the remote machine 30 the components, modules and subsystems describedabove in connection with FIG. 79.

The network module 7920 receives authentication information associatedwith a user operating a client machine, such as client machine 10. Insome embodiments, the network module 7920 is in communication with anauthentication module for authenticating the user in response to thereceived authentication information. In other embodiments, the networkmodule 7920 includes the authentication module.

The data store 7926 contains an identifier of a computing environmentassociated with the user. In one embodiment, the data store 7926contains a first identifier of a first computing environment associatedwith the user and a second identifier of a second computing environmentassociated with the user. In another embodiment the first computingenvironment executes on a first remote machine 30 and the secondcomputing environment executes on a second remote machine 30′. In someof these embodiments, the broker process 8532 transmits the enumerationfrom the data store to the client machine 10.

The broker process 8532 connects the client machine 10 to the identifiedcomputing environment enumerated in the data store 7926, in response tothe received information. In one embodiment, the broker process 8532connects the client machine 10 to the identified computing environmentsubject to a rule. In another embodiment, the broker process 8532disconnects the client machine 10 from the identified computingenvironment in response to a received disconnect signal. In stillanother embodiment, the broker process 8532 updates a data recordassociated with the identified computing environment to indicate theclient machine 10 is disconnected from the identified computingenvironment.

In some embodiments, the remote machine 30 includes a collection agentand a policy engine. In one of these embodiments, the collection agentgathers information about the client machine 10. In another of theseembodiments, the collection agent comprises at least one script. Instill another of these embodiments, the collection agent comprisesbytecode. In yet another of these embodiments, the collection agentgathers the information by running at least one script on the clientmachine 10. In some of these embodiments, the collection agent executeson the client machine 10. In others of these embodiments, the collectionagent is transmitted to the client machine 10. In one of theseembodiments, the policy engine transmits the collection agent to theclient machine 10.

In some of these embodiments, the remote machine 30 includes a policyengine receiving the gathered information and assigning one of aplurality of levels of access responsive to application of a policy tothe received information, the broker process 8532 connecting the clientmachine to the identified computing environment enumerated in the datastore responsive to the assigned access level. In one embodiment, thepolicy engine further comprises a database storing configurablepolicies. In another embodiment, the policy engine transmitsinstructions to the collection agent determining the type of informationthe collection agent gathers.

In others of these embodiments, the policy engine further comprises alogon agent. In one of these embodiments, the logon agent receives thegathered information from the collection agent. In another of theseembodiments, the logon agent identifies for the policy engineauthentication information received from the collection agent. In stillanother of these embodiments, the policy engine further comprises aplurality of logon agents. In yet another of these embodiments, at leastone of the plurality of logon agents resides on each network domain fromwhich a client machine 10 may transmit a resource request. In someembodiments, the client machine 10 transmits the resource request to aparticular logon agent. In other embodiments, the logon agent identifiesfor the policy engine the network domain from which the client machinetransmits the resource request.

In some embodiments, a virtual machine farm provides functionality forrelocating a session from one requesting machine to a second requestingmachine. In one of these embodiments, the virtual machine farm providesaccess to information required for relocating a session. In another ofthese embodiments, a hypervisor provides functionality for relocating avirtual machine session. In some embodiments, the hypervisor implementswell-known techniques, including pre-copying, post-copying, andlazy-copying for moving session information associated with a virtualmachine session from one execution machine to a second executionmachine.

In some embodiments, the virtual machine farm is in communication with asystem as described in FIG. 86 and FIG. 87, and provides functionalityfor relocation of an application session within a virtual machinesession.

Referring to FIG. 86, one embodiment of a network constructed inaccordance with the invention is depicted, which includes a clientmachine 10, a collection agent 704, a policy engine 706, a policydatabase 708, a condition database 710, a client machine 10′, a sessionserver 8620, a stored application database 8622, a remote machine 30′, afirst database 8628, a remote machine 30″, and a second database 8632.In brief overview, when the client machine 10 transmits to the policyengine 706 a request 206 for access to an application program, thecollection agent 704 communicates with client machine 10, retrievesinformation about client machine 10, and transmits client machineinformation 714 to the policy engine 706. The policy engine 706 makes anaccess control decision, as discussed above in FIG. 7A and FIG. 7B. Theclient machine 10 receives an enumeration of available applicationsassociated with the client machine 10.

In some embodiments, the session server 8620 establishes a connectionbetween the client machine 10 and a plurality of application sessionsassociated with the client machine 10. In one of these embodiments, theconnection is established to a virtual machine providing access to acomputing environment in which the application sessions execute. Inother embodiments, the policy engine 706 determines that the clientmachine 10 has authorization to retrieve a plurality of applicationfiles comprising the application and to execute the application programlocally. In one of these embodiments, the remote machine 30′ storesapplication session data and a plurality of application files comprisingthe application program. In another of these embodiments, the clientmachine 10 establishes an application streaming session with a remotemachine 30′ storing the application session data and the plurality ofapplication files comprising the application program.

Referring now to FIG. 87, a flow diagram depicts one embodiment of thesteps taken by the session server 8620 to provide access for the clientmachine 10 to its associated application sessions. The session server8620 receives information about the client machine 10 from the policyengine 706 containing the access control decision the policy engine 706made (step 8780). In one embodiment, the information also includes theclient machine information 714. In another embodiment, the informationincludes authorization to execute the application program locally. Instill another embodiment, the information includes authorization toprovide access to computing environment in which the application programexecutes.

In some embodiments, the policy engine 706 identifies a plurality ofapplication sessions already associated with the client machine 10. Inother embodiments, the session server 8620 identifies stored applicationsessions associated with the client machine 10 (step 8782). In some ofthese embodiments, the session server 8620 automatically identifies thestored application sessions upon receiving the information from thepolicy engine 706. In one embodiment, the stored application database8622 resides on the session server 8620. In another embodiment, thestored application database 8622 resides on the policy engine 706.

The stored application database 8622 contains data associated with aplurality of machines 30 in the machine farm 38 executing applicationsessions or providing access to application session data and applicationfiles comprising application programs, or providing access to computingenvironments in which application sessions may execute, includingvirtual machines which may be active, suspended, paused or disconnected.In some embodiments, identifying the application sessions associatedwith the client machine 10 requires consulting stored data associatedwith one or more machines 30. In some of these embodiments, the sessionserver 8620 consults the stored data associated with one or moremachines 30. In others of these embodiments, the policy engine 706consults the stored data associated with one or more machines 30. Insome embodiments, a first application session runs on a remote machine30′ and a second application session runs on a remote machine 30″. Inother embodiments, all application sessions run on a single remotemachine 30 within the machine farm 38. In still other embodiments one ormore application sessions run on a remote machine 30 executing a virtualmachine providing access to a computing environment in which theapplication sessions execute.

The session server 8620 includes information related to applicationsessions initiated by users. The session server can be stored involatile or non-volatile memory or, for example, distributed throughmultiple servers. Table 4 shows the data included in a portion of anillustrative session server 8620: TABLE 4 Application Session AppSession 1 App Session 2 App Session 3 User ID User 1 User 2 User 1Client ID First Client First Client Client Address 172.16.0.50172.16.0.50 Status Active Disconnected Active Applications WordProcessor Data Base Spreadsheet Process Number 1 3 2 Server Server AServer A Server B Server Address 172.16.2.55 172.16.2.55 172.16.2.56Executing in a Yes (Instance No no Virtual Machine? ID #)

The session server 8620 in Table 4 includes data associating eachapplication session with the user that initiated the applicationsession, an identification of the client machine 10, if any, from whichthe user is currently connected to the remote machine 30′, and the IPaddress of that client computer 10. The session server 8620 alsoincludes the status of each application session. The data may include anidentification of a virtual machine providing a computing environment inwhich the application session executes. An application session statuscan be, for example, “active” (meaning a user is connected to theapplication session), or “disconnected” (meaning a user is not connectedto the application session). In an alternative embodiment, anapplication session status can also be set to “executing-disconnected”(meaning the user has disconnected from the application session, but theapplications in the application session are still executing), or“stalled-disconnected” (meaning the user is disconnected and theapplications in the application session are not executing, but theiroperational state immediately prior to the disconnection has beenstored). The session server 8620 further stores information indicatingthe application 7916 that are executing within each application sessionand data indicating each application's process on the server. Forembodiments in which the session is hypervisor-based, the session server8620 may store an identification of a hypervisor domain or a virtualmachine instance identifier. In embodiments in which the remote machine30′ is part of the machine farm 38, the session server 8620 is at leasta part of the dynamic store in addition to the data in the last threerows of Table 4 that identify a remote machine 30 in the machine farm 38on which each application is/was executing, and the IP address of thatremote machine 30. In alternative embodiments, the session server 8620includes a status indicator for each application in each applicationsession.

For example, in the example of Table 4, three application sessionsexist, App Session 1, App Session 2, and App Session 3. App Session 1 isassociated with User 1, who is currently using terminal 1. Terminalone's IP address is 172.16.2.50. The status of App Session 1 is active,and in App Session 1, a word processing program, is being executed. Theword processing program is executing on Server A as process number 1.Server A's IP address is 172.16.2.55. App Session 2 in Table 1 is anexample of a disconnected application session 7918. App Session 2 isassociated with User 2, but App Session 2 is not connected to a clientmachine 10 or 20. App Session 2 includes a database program that isexecuting on Server A, at IP address 152.16.2.55 as process number 3.App Session 3 is an example of how a user can interact with applicationsessions operating on different remote machines 30. App Session 3 isassociated with User 1, as is App Session 1. App Session 3 includes aspreadsheet program that is executing on Server B at IP address152.16.2.56 as process number 2, whereas the application sessionincluded in App Session 1 is executing on Server A. Although only oneApp Session 1 is described in the application session, the applicationsession may comprise a plurality of executing resources, includingapplication sessions executing in computing environments and computingenvironments executing in a virtual machine.

In another example, a user may access a first application programthrough an application session executing on a remote machine 30′, suchas Server A, while communicating across an application streaming sessionwith a second remote machine 30″, such as Server B, to retrieve a secondapplication program from the second remote machine 30″ for localexecution. The user of the client machine 10 may have acquiredauthorization to execute the second application program locally whilefailing to satisfy the local execution pre-requisites of the firstapplication program.

In one embodiment, the session server 8620 is configured to receive adisconnect request to disconnect the application sessions associatedwith the client machine 10 and disconnects the application sessions inresponse to the request. The session server 8620 continues to execute anapplication session after disconnecting the client machine 10 from theapplication session. In this embodiment, the session server 8620accesses the stored application database 8622 and updates a data recordassociated with each disconnected application session so that the recordindicates that the application session associated with the clientmachine 10 is disconnected.

After receiving authentication information associated with a clientmachine 10 connecting to the network, the session server 8620 consultsthe stored applications database 8622 to identify any active applicationsessions that are associated with a user of the client machine 10, butthat are connected to a different client machine 10, such as the clientmachine 10 if the authentication information is associated with clientmachine 10′, for example. In one embodiment, if the session server 8620identifies any such active application sessions, the session server 8620automatically disconnects the application session(s) from the clientmachine 10 and connects the application session(s) to the current clientmachine 10′ (step 8784). In some embodiments, the receivedauthentication information will restrict the application sessions towhich the client machine 10 may reconnect. In other embodiments, thereceived authentication information authorizes execution of anapplication program on the client machine 10′, where the authorizationmay have been denied to client machine 10. In one of these embodiments,the session server 8620 may provide the client machine 10 accessinformation for retrieving the application program for second execution.In still other embodiments, the received authentication informationauthorizes execution of an application program in a computingenvironment provided by a virtual machine.

Referring now to FIG. 88, a block diagram depicts one particularembodiment of a system for providing, by a virtual machine access to acomputing environment. A client agent 8802 on a client machine 10connects to a remote machine 30. In some embodiments, the client agent8802 establishes a connection with a session management component 1300.In other embodiments, the session management component 1300 is executedby the remote machine 30 to which the client machine 10 connects. In oneembodiment, the session management component 1300 queries a virtualmachine management component 1200, for the location of the configurationand virtual disk files of a virtual machine to run for the current userand a hypervisor in which the virtual machine may execute. In someembodiments, the identified hypervisor and virtual machine execute onremote machine 30. In other embodiments, the identified hypervisor andvirtual machine execute on a remote machine 30′. In one embodiment, thesession management component launches the virtual machine within thespecified hypervisor in full screen mode. In another embodiment, apreviously-executing virtual machine is allocated to the client machine10.

In some embodiments, a virtual machine service component 8804 executeswithin a computing environment provided by a virtual machine on a remotemachine 30. In one of these embodiments, the virtual machine servicecomponent 8804 receives an IP address and a port with which to establisha communication channel between the session management component 1300and the virtual machine service component 8804. In one embodiment, thiscommunication channel is used to pass session related configurationinformation from the client agent session into the virtual machinesession. In some embodiments, the configuration information includesdisplay settings and changes, client drive information andauthentication data with which to enable single sign-on for a user ofthe client machine 10.

In some embodiments, once the communications channel is established andthe initial session related information is passed to the virtual machineservice component 8804, the virtual machine service component 8804automatically connects the user to a computing environment, such as aguest operating system, using the same credentials as were provided tothe client agent 8802 by the user (if any). In one of these embodiments,the virtual machine service component 8804 automatically reconfiguresthe display settings of the guest operating system to match those of theclient 8802. The virtual machine produces graphics and sound output tovirtual devices that redirect that output, directly or indirectly, tothe client agent 8802 on the client machine 10. The virtual machinereceives audio input, mouse and keyboard device data redirected from theclient machine 10. When the virtual machine is shutdown or suspended thesession management component 1300 terminates the client agent session.

Referring now to FIG. 95, a block diagram depicts one embodiment of asystem for providing to a first client agent, via a second client agenton a first remote machine, output data generated by a resource executingin a virtual machine provided by a second remote machine. A client agent8802 on a client machine 10 connects to a remote machine 30 and requestsaccess to a resource. In one embodiment, the remote machine 30 is anintermediate machine. In another embodiment, the remote machine 30determines to provide access to the requested resource via a virtualmachine. In still another embodiment, the remote machine 30 identifies aremote machine 30′ to provide access to the requested resource via avirtual machine executing on the remote machine 30′. The remote machine30′ may be referred to as an execution machine 30′.

In one embodiment, the client machine 10 communicates with the remotemachine 30 using a presentation layer protocol, such as ICA, RDP, VNC,or X11. In some embodiments, protocol stacks are implemented to enablecommunications between the client machine 10 and remote machines 30, asdescribed above in connection with FIG. 8, step 816 and with FIG. 24.

In one embodiment, an agent 8802′ on the remote machine 30 establishes aconnection to the remote machine 30′. In another embodiment, the remotemachine 30 communicates with the remote machine 30′ using a presentationlayer protocol, such as ICA, RDP, VNC, or X11. In still anotherembodiment, the remote machine 30 establishes a connection with theremote machine 30′ and communicates with the remote machine 30′ using apresentation layer protocol, such as RDP, from within a terminalservices session executing on the remote machine 30. In someembodiments, protocol stacks are implemented to enable communicationsbetween the agent 8802′ on the remote machine 30 and the remote machine30′, as described above in connection with FIG. 8, step 816 and withFIG. 24.

In one embodiment, as depicted by FIG. 95, the remote machine 30′provides access to the requested resource by providing access to avirtualized environment or by providing access to an applicationstreaming service, as described above in connection with FIG. 8. Inanother embodiment, the remote machine 30′ executes the resource in avirtual machine executing on the remote machine 30′. In still anotherembodiment, the remote machine 30′ transmits output data generated bythe execution of the resource to the remote machine 30 using apresentation layer protocol. In another embodiment, the remote machine30 forwards the output data received from the remote machine 30′ to theclient machine 10 using a presentation layer protocol. In someembodiments, the virtual machine executes on the remote machine 30′. Inother embodiments, the virtual machines execute on a remote machine 30″.

In one embodiment, the remote machine 30′ provides access to a publisheddesktop computing environment. In another embodiment, the remote machine30′ provides access to a published desktop computing environmentselected from an enumeration of a plurality of published desktopcomputing environments available to the client machine 10. In someembodiments, as described above in connection with the description ofthe virtual machine management component 1200, virtual machines mayprovide access to standard operating environments.

Referring now to FIG. 96, a block diagram depicts an embodiment of asystem for providing to a first client agent, via a second client agenton a first remote machine, output data generated by a resource executingin a virtual machine provided by a second remote machine. A client agent8802 on a client machine 10 connects to a remote machine 30 and requestsaccess to a resource. In one embodiment, the remote machine 30 is anintermediate machine. In another embodiment, the remote machine 30determines to provide access to the requested resource via a virtualmachine. In still another embodiment, the remote machine 30 identifies aremote machine 30′ to provide access to the requested resource via avirtual machine executing on the remote machine 30′. The remote machine30′ may be referred to as an execution machine 30′.

In one embodiment, the client machine 10 communicates with the remotemachine 30 using a presentation layer protocol, such as ICA, RDP, VNC,or X11. In some embodiments, protocol stacks are implemented to enablecommunications between the client machine 10 and remote machines 30, asdescribed above in connection with FIG. 8, step 816 and with FIG. 24.

In one embodiment, an agent 8802′ on the remote machine 30 establishes aconnection to the remote machine 30′. In another embodiment, the remotemachine 30 communicates with the remote machine 30′ using a presentationlayer protocol, such as ICA, RDP, VNC, or X11. In still anotherembodiment, the remote machine 30 establishes a connection with theremote machine 30′ and communicates with the remote machine 30′ using apresentation layer protocol, such as ICA. In some embodiments, protocolstacks are implemented to enable communications between the agent 8802′on the remote machine 30 and the remote machine 30′, as described abovein connection with FIG. 8, step 816 and with FIG. 24.

In one embodiment, as depicted by FIG. 96, the remote machine 30′provides access to the requested resource by providing access to avirtualized environment or by providing access to an applicationstreaming service, as described above in connection with FIG. 8. Inanother embodiment, the remote machine 30′ executes the resource in avirtual machine executing on the remote machine 30′. In still anotherembodiment, the remote machine 30′ transmits output data generated bythe execution of the resource to the remote machine 30 using apresentation layer protocol. In another embodiment, the remote machine30 forwards the output data received from the remote machine 30′ to theclient machine 10 using a presentation layer protocol. In someembodiments, the virtual machine executes on the remote machine 30′. Inother embodiments, the virtual machines execute on a remote machine 30″.

Referring now to FIG. 97, a block diagram depicts one embodiment of asystem for identifying, by a coordinator machine, a worker machineproviding, via a virtual machine, access to a computing environment. Aclient agent 8802 on a client machine 10 connects to a remote machine 30and requests access to a resource. In one embodiment, the remote machine30 is a coordinator machine, providing the functionality of anintermediate broker machine. In another embodiment, the remote machine30 identifies a remote machine 30′ to provide access to the requestedresource.

In some embodiments, the remote machine 30 is a remote machine in aplurality of remote machines functioning as intermediate brokermachines. In one of these embodiments, the coordinator machines receiverequests and identify other remote machines 30′ from a second pluralityof remote machines, the identified machines responding to the requests.In another of these embodiments, the identified remote machines 30′ arereferred to as worker machines. In still another of these embodiments,the client machine 10 communicates with the coordinator machine 30 usinga presentation layer protocol, such as ICA, RDP, VNC, or X11.

In one embodiment, the coordinator machine 30 identifies a pool ofworker machines 30′ each capable of providing access to the requestedresource. In some embodiments, the coordinator machine 30 identifies aworker machine 30′ from the pool of worker machines 30′ capable ofproviding access to the requested resource. In other embodiments, thecoordinator machine 30 identifies a worker machine 30′ and transmitsinformation for accessing the worker machine 30′ to the client machine10. In still other embodiments, the coordinator machine 30 transmitsinformation for accessing the client machine 10 to the worker machine30′. In one of these embodiments, the coordinator machine 30 provides noadditional information or communication to the client machine 10 aftertransmitting the access information associated with the worker machine30′. In yet other embodiments, the coordinator machine 30 establishes aconnection between the client machine 10 and a worker machine 30′.

In one embodiment, the client agent 8802 of the client machine 10establishes a connection to the worker machine 30′. In anotherembodiment, the client machine 10 communicates with the worker machine30′ using a presentation layer protocol, such as ICA, RDP, VNC, or X11.

In some embodiments, the worker machine 30′ provides access to therequested resource by executing an application on the worker machine 30′and transmitting application-output data generated by the execution ofthe application to the client 10. In other embodiments, as depicted byFIG. 97, the worker machine 30′ provides access to the requestedresource by providing access to a virtualized environment or byproviding access to an application streaming service, as described abovein connection with FIG. 8.

In some embodiments, upon identification of a worker machine 30′, theclient agent 8802 of the client machine 10 establishes a connection witha session management component 1300 associated with or residing on theworker machine 30′. In other embodiments, the worker machine 30′executes the session management component 1300 to which the clientmachine 10 connects. In one embodiment, the session management component1300 queries a virtual machine management component 1200, for thelocation of the configuration and virtual disk files of a virtualmachine to run for the current user and a hypervisor in which thevirtual machine may execute. In still other embodiments, the clientmachine 10 connects directly to the worker machine 30′.

In some embodiments, the identified hypervisor and virtual machineexecute on the worker machine 30′. In other embodiments, the identifiedhypervisor and virtual machine execute on a remote machine 30″. In oneof these embodiments, the worker machine 30′ communicates with theremote machine 30″ using a presentation layer protocol to receive outputdata generated by a resource executed by the virtual machine.

In one embodiment, the session management component launches the virtualmachine within the specified hypervisor in full screen mode. In anotherembodiment, a previously-executing virtual machine is allocated to theclient machine 10.

In some embodiments, a virtual machine service component 8804 executeswithin a computing environment provided by a virtual machine on a workermachine 30′. In one of these embodiments, the virtual machine servicecomponent 8804 receives an IP address and a port with which to establisha communication channel between the session management component 1300and the virtual machine service component 8804. In one embodiment, thiscommunication channel is used to pass session related configurationinformation from the client agent session into the virtual machinesession. In some embodiments, the configuration information includesdisplay settings and changes, client drive information andauthentication data with which to enable single sign-on for a user ofthe client machine 10.

In some embodiments, once the communications channel is established andthe initial session related information is passed to the virtual machineservice component 8804, the virtual machine service component 8804automatically connects the user to a computing environment, such as aguest operating system, using the same credentials as were provided tothe client agent 8802 by the user (if any). In one of these embodiments,the virtual machine service component 8804 automatically reconfiguresthe display settings of the guest operating system to match those of theclient 10. The virtual machine produces graphics and sound output tovirtual devices that redirect that output, directly or indirectly, tothe client agent 8802 on the client machine 10. The virtual machinereceives audio input, mouse and keyboard device data redirected from theclient machine 10. When the virtual machine is shutdown or suspended thesession management component 1300 terminates the client agent session.

In some embodiments, the coordinator machine 30 provides functionalityfor managing a pool of worker machines 30′. In one of these embodiments,for example, the coordinator machine 30 receives information identifyingthe worker machines 30′ as physical machines providing access toparticular resources, or as virtual machines providing access toparticular resources. In another of these embodiments, the coordinatormachine 30 receives information identifying a plurality of types ofresources provided by the pool of worker machines 30′. For example, thecoordinator machine 30 may receive information identifying a pool ofworker machines 30′ as providing access to a type of computingenvironment, such as a desktop or application. In still another of theseembodiments, the coordinator machine 30 communicates with a virtualmachine management component 1200 to receive information about virtualmachines in the pool of worker machines 30′.

In other embodiments, the coordinator machine 30 monitors one or moreworker machines 30′ in the pool of worker machines 30′. In one of theseembodiments, the coordinator machine 30 identifies a worker machine 30′to provide access to a resource for a client machine 10 and identifies aworker machine 30″ to provide access to the resource upon a failure ofthe worker machine 30′. In another of these embodiments, the coordinatormachine 30 identifies a worker machine 30″ to provide access to theresource responsive to a load balancing technique. In still another ofthese embodiments, the coordinator machine 30 identifies a workermachine 30″ to provide access to the resource responsive to a changeassociated with the client machine 10. For example, the coordinatormachine 30 may identify a first worker machine 30′ to provide access tothe resource for the client machine 10 and the receive a second requestfor access by the client machine 10, after the client machine 10 hasestablished a connected via a different network, or has lost a firstnetwork connection and re-established a second network connection.

In some embodiments, the coordinator machine 30 identifies a workermachine 30 that provides access to a resource for a client machine 10according to a method chosen responsive to an evaluation of the clientmachine 10, an application of a policy to the client machine 10 and tothe worker machine 30′, and an evaluation of the capabilities andrequirements of the resource, the client machine 10 and the workermachine 30′.

The previously described embodiments may be implemented as a method,apparatus or article of manufacture using programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The term “article of manufacture” as used herein is intended toencompass code or logic accessible from and embedded in one or morecomputer-readable devices, firmware, programmable logic, memory devices(e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,floppy disk, hard disk drive, etc.), a file server providing access tothe programs via a network transmission line, wireless transmissionmedia, signals propagating through space, radio waves, infrared signals,etc. The article of manufacture includes hardware logic as well assoftware or programmable code embedded in a computer readable mediumthat is executed by a processor. Of course, those skilled in the artwill recognize that many modifications may be made to this configurationwithout departing from the scope of the present invention.

Having described certain embodiments of methods and systems forproviding access to a computing environment, it will now become apparentto one of skill in the art that other embodiments incorporating theconcepts of the invention may be used. Therefore, the invention shouldnot be limited to certain embodiments, but rather should be limited onlyby the spirit and scope of the following claims.

1. A method of providing access to a computing environment, the methodcomprising the steps of: (a) receiving, by a broker machine, a requestfrom a client machine for access to a computing environment, the requestincluding an identification of a user of the client machine; (b)identifying one of a plurality of virtual machines, the identifiedvirtual machine providing the requested computing environment; (c)identifying one of a plurality of execution machines, the identifiedexecution machine executing a hypervisor providing access to hardwareresources required by the identified virtual machine; and (d)establishing a connection between the client machine and the identifiedvirtual machine.
 2. The method of claim 1, wherein step (b) furthercomprises identifying one of the plurality of virtual machinesresponsive to the received identification of the user of the clientmachine.
 3. The method of claim 1, wherein step (b) further comprisesidentifying one of the plurality of virtual machines responsive to arequest by the client machine for a type of virtual machine.
 4. Themethod of claim 1, wherein step (b) further comprises identifying one ofthe plurality of virtual machines responsive to a request by the clientmachine for a type of computing environment.
 5. The method of claim 1,wherein step (b) further comprises identifying, by the sessionmanagement component, one of the plurality of virtual machines, theidentified virtual machine executing in the hypervisor.
 6. The method ofclaim 1, wherein step (c) further comprises provisioning, by thehypervisor, a plurality of hardware resources on the identifiedexecution machine for use by the identified virtual machine.
 7. Themethod of claim 1, wherein step (c) further comprises partitioning, bythe hypervisor, a plurality of hardware resources on the identifiedexecution machine for use by the identified virtual machine.
 8. Themethod of claim 1, wherein step (c) further comprises identifying theone of the plurality of execution machines responsive to anidentification of hardware resources required by the identified virtualmachine.
 9. The method of claim 1, wherein step (c) further comprisesidentifying, by the broker machine, one of the plurality of executionmachines.
 10. The method of claim 1, wherein step (d) further comprisesproviding an internet protocol address associated with the identifiedvirtual machine to the client machine.
 11. The method of claim 1,wherein step (d) further comprises providing an internet protocoladdress associated with the identified execution machine to the clientmachine.
 12. The method of claim 1, wherein step (d) further comprisesproviding a proxy for communication between the client machine and theidentified virtual machine.
 13. The method of claim 1, wherein step (d)further comprises launching the identified virtual machine in thehypervisor.
 14. The method of claim 1, wherein step (d) furthercomprises establishing a connection between the client machine and theidentified virtual machine using a presentation layer protocol.
 15. Anapparatus, in a system providing access to a computing environment by abroker machine to a client machine, an execution machine executing ahypervisor providing access to hardware resources required by thecomputing environment, the apparatus comprising: an identificationcomponent in communication with a virtual machine management componentand receiving an identification of one of a plurality of virtualmachines, the identified virtual machine providing a requested computingenvironment; an execution component provisioning the identified virtualmachine; and a management component establishing a connection betweenthe client machine and the identified virtual machine.
 16. The apparatusof claim 15 further comprising a virtual machine service componentexecuting in the hypervisor, the virtual machine service component incommunication with the session management component and receivingconfiguration information associated with the client machine.
 17. Theapparatus of claim 15 further comprising a virtual machine servicecomponent executing in the identified virtual machine, the virtualmachine service component in communication with the session managementcomponent and receiving configuration information associated with theclient machine.
 18. The apparatus of claim 15, wherein theidentification component receives from the virtual machine managementcomponent the identification of the one of the plurality of virtualmachines.
 19. The apparatus of claim 15, wherein the identificationcomponent identifies one of a plurality of execution machines, ahypervisor executing on the identified execution machine.
 20. Theapparatus of claim 15, wherein the identification component identifiesone of a plurality of execution machines, the identification componentlaunching the identified virtual machine into a hypervisor executing onthe identified execution machine.
 21. The apparatus of claim 15, whereinthe identification component receives an identification of one of aplurality of execution machines.
 22. The apparatus of claim 15, whereinthe identification component receives from the broker machine anidentification of one of a plurality of execution machines.
 23. Theapparatus of claim 15, wherein the identification component furthercomprises a transceiver receiving an identification of a user of theclient machine and transmitting the identification of the user to thevirtual machine management component.
 24. The apparatus of claim 15,wherein the identification component further comprises a transceiverreceiving an identification by a user of the client machine of a type ofcomputing environment requested and transmitting the identification ofthe type of computing environment requested to the virtual machinemanagement component.
 25. The apparatus of claim 15, wherein theidentification component further comprises a transceiver receiving anidentification by a user of the client machine of a type of virtualmachine requested and transmitting the identification of the type ofvirtual machine requested to the virtual machine management component.26. The apparatus of claim 15, wherein the identification componentfurther comprises a transceiver receiving an identification of a type ofcomputing environment requested and transmitting the identification ofthe type of computing environment requested to the virtual machinemanagement component.
 27. The apparatus of claim 15, wherein theidentification component further comprises a transceiver receiving anidentification of a type of virtual machine requested and transmittingthe identification of the type of virtual machine requested to thevirtual machine management component.
 28. The apparatus of claim 15,wherein the identification component further comprises receiving anidentification of one of a plurality of virtual machines, the identifiedvirtual machine already executing in the hypervisor on the executionmachine.
 29. The apparatus of claim 15, wherein the identificationcomponent receives an identification of one of a plurality of virtualmachines, the identified virtual machine selected responsive to areceived identification of a user of the client machine.
 30. Theapparatus of claim 15, wherein the identification component receives anidentification of one of a plurality of virtual machines, the identifiedvirtual machine selected responsive to a received identification of atype of computing environment requested.
 31. The apparatus of claim 15,wherein the identification component receives an identification of oneof a plurality of virtual machines, the identified virtual machineselected responsive to a received identification of a type of virtualmachine requested.
 32. The apparatus of claim 15, wherein the executioncomponent comprises launching the identified virtual machine into thehypervisor.
 33. The apparatus of claim 15, wherein the virtual machinemanagement component allocates the identified virtual machine to a user.34. The apparatus of claim 15, wherein the management component furthercomprises providing an internet protocol address associated with theidentified virtual machine to the client machine.
 35. The apparatus ofclaim 15, wherein the management component further comprises providingan internet protocol address associated with the execution machine tothe client machine.
 36. The apparatus of claim 15, wherein themanagement component further comprises providing a proxy forcommunication between the client machine and the virtual machine. 37.The apparatus of claim 15, wherein the management component furthercomprises establishing a connection between the client machine and thevirtual machine using a presentation layer protocol.